Report indexing status to SDR during geo indexing #1311
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thatbudakguy
force-pushed
the
report-indexing-events
branch
from
5658c54 to
b13cfe3
Compare
thatbudakguy
force-pushed
the
report-indexing-events
branch
from
b13cfe3 to
e00b0d5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1299
I tested this with some geo content in argo-stage. Druid bd882yq4680 successfully received a message from the indexer:
Druid yy029tb6261 was not indexed because the indexer couldn't transform its bounding box into valid data at index-time, and it received an appropriate message: