Skip to content

Change log msg from warn to debug level. Added what maxDocBatchSize is in the msg #1291 #1300

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 10, 2021
Merged

Change log msg from warn to debug level. Added what maxDocBatchSize is in the msg #1291 #1300

merged 1 commit into from
Jun 10, 2021

Conversation

llinggit
Copy link
Contributor

So we can incorporate your pull request, please share the following:

  • What issue are you addressing with this pull request? docBatchSize warning is confusing #1291
  • Are you modifying the correct branch? (See CONTRIBUTING.md) yes, develop
  • Have you run unit tests? (See CONTRIBUTING.md) yes, ran QueryBatcherTest.java. All tests passed.
  • Version of MarkLogic Java Client API (see Readme.txt) nightly
  • Version of MarkLogic Server (see admin gui on port 8001) 10.0
  • Java version (java -version) 8
  • OS and version Mac
  • What Changed: What happened before this change? What happens without this change? - Before the error msg is at warn level, but now at debug level. Also added in the msg what maxDocBatchSize is. Now the logs look like "[Test worker] DEBUG c.m.c.d.impl.QueryBatcherImpl - docBatchSize is beyond maxDocBatchSize, which is 2048."

@llinggit llinggit requested review from ehennum and anu3990 June 10, 2021 05:48
@llinggit llinggit self-assigned this Jun 10, 2021
@llinggit llinggit merged commit 3f45276 into marklogic:develop Jun 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@anu3990 anu3990 anu3990 approved these changes

@ehennum ehennum Awaiting requested review from ehennum

Assignees

@llinggit llinggit

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@llinggit @anu3990