-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QueryIterators/ScanIterators should log query id first #2305
Comments
SethSmucker
added a commit
to SethSmucker/datawave
that referenced
this issue
Jun 5, 2024
Added the query option tserver.logging.active to enable logging of query IDs to the TServer logs. Created the class QueryLogIterator to handle this. Logs the start and end of each method called. Fixes NationalSecurityAgency#2305
SethSmucker
added a commit
to SethSmucker/datawave
that referenced
this issue
Jun 6, 2024
Added the query option tserver.logging.active to enable logging of query IDs to the TServer logs. Created the class QueryLogIterator to handle this. Logs the start and end of each method called. Fixes NationalSecurityAgency#2305
This was referenced Jun 7, 2024
SethSmucker
added a commit
to SethSmucker/datawave
that referenced
this issue
Jun 20, 2024
Added the query option tserver.logging.active to enable logging of query IDs to the TServer logs. Created the class QueryLogIterator to handle this. Logs the start and end of each method called. Fixes NationalSecurityAgency#2305
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need the query id logged in the Tserver logs as soon as the scan starts and again when the scan completes. As a bonus it would be great if we could add the queryid to the thread name as well while it is executing.
The text was updated successfully, but these errors were encountered: