[jira] [Updated] (OAK-6333) IndexPlanner should use actual entryCount instead of limiting it to 1000

[ https://issues.apache.org/jira/browse/OAK-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-6333: - Fix Version/s: 1.2.28 > IndexPlanner should use actual entryCount instead of limiting it to 1000 > -

[jira] [Updated] (OAK-6333) IndexPlanner should use actual entryCount instead of limiting it to 1000

[ https://issues.apache.org/jira/browse/OAK-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-6333: - Labels: (was: candidate_oak_1_4 candidate_oak_1_6) Fix Version/s: 1.4.18

[jira] [Updated] (OAK-6333) IndexPlanner should use actual entryCount instead of limiting it to 1000

[ https://issues.apache.org/jira/browse/OAK-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-6333: - Labels: candidate_oak_1_4 candidate_oak_1_6 (was: ) > IndexPlanner should use actual entryCount ins

[jira] [Updated] (OAK-6333) IndexPlanner should use actual entryCount instead of limiting it to 1000

[ https://issues.apache.org/jira/browse/OAK-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-6333: - Description: Currently IndexPlanner uses following logic for estimating the entryCount # If the ind

[jira] [Updated] (OAK-6333) IndexPlanner should use actual entryCount instead of limiting it to 1000

[ https://issues.apache.org/jira/browse/OAK-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-6333: - Description: Currently IndexPlanner uses following logic for estimating the entryCount # If the ind