-
Notifications
You must be signed in to change notification settings - Fork 35
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
Improve logging #218
Comments
How about an info message when the linkage action takes place since linkage can take a lot of time? I just saw that you are using the "cartesian" linkage method. Does the broadcastjoin approach does not work for you? Cartesian could be very slow if you don't have a lot of resources.
This is related to #190 . |
Could you please clarify this?
Sadly I can't do this as I need to use the Query Builders with the "link" method and it is not supported as we discussed in pull request #162
|
Is your feature request related to a problem? Please describe.
I would be nice to have more logs to understand what is going on with the application. Sometimes it seems stuck.
Even with the log level set to DEBUG there is not a lot of information to trace the progress. For example, consider the following logging configuration :
And the log messages :
After the documents , are indexed , there is no information about what is happening on the cluster/process. I'd be nice to be able to trace the process even deeper
The text was updated successfully, but these errors were encountered: