pranavbhole opened a new pull request, #15744:
URL: https://github.com/apache/druid/pull/15744

   Reverts https://github.com/apache/druid/pull/15336 
   
   ###  Revert PR Description: 
   A low value of inSubQueryThreshold can cause queries with IN filter to plan 
as joins more commonly. However, some of these join queries may not get planned 
as IN filter on data nodes and causes significant perf regression.
   We had reverted this default value of inSubQueryThreshold to 20, causing in 
filters with more elements to be planned as joins instead of OR filters, thus 
reverting it back to Integer.MAX_VALUE. We still need to find the best number 
for this value.
   
   The default inSubQueryThreshold is Integer.MAX_VALUE. This was chosen at the 
time to maintain the then current behavior. However, this value is too high for 
most cases, and significant slowdown has been observed for large number of 
values, compared to joins.
   
   This PR has:
   
   - [ ] been self-reviewed.
      - [ ] using the [concurrency 
checklist](https://github.com/apache/druid/blob/master/dev/code-review/concurrency.md)
 (Remove this item if the PR doesn't have any relation to concurrency.)
   - [ ] added documentation for new or modified features or behaviors.
   - [ ] a release note entry in the PR description.
   - [ ] added Javadocs for most classes and all non-trivial methods. Linked 
related entities via Javadoc links.
   - [ ] added or updated version, license, or notice information in 
[licenses.yaml](https://github.com/apache/druid/blob/master/dev/license.md)
   - [ ] added comments explaining the "why" and the intent of the code 
wherever would not be obvious for an unfamiliar reader.
   - [ ] added unit tests or modified existing tests to cover new code paths, 
ensuring the threshold for [code 
coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md)
 is met.
   - [ ] added integration tests.
   - [ ] been tested in a test Druid cluster.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to