[jira] Updated: (LUCENE-1541) Trie range - make trie range indexing more flexible
[ https://issues.apache.org/jira/browse/LUCENE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1541: --- Fix Version/s: (was: 2.9) 3.1 OK, moving out to 3.1. Trie range - make trie range indexing more flexible --- Key: LUCENE-1541 URL: https://issues.apache.org/jira/browse/LUCENE-1541 Project: Lucene - Java Issue Type: Improvement Components: contrib/* Affects Versions: 2.9 Reporter: Ning Li Assignee: Uwe Schindler Priority: Minor Fix For: 3.1 Attachments: LUCENE-1541.patch, LUCENE-1541.patch In the current trie range implementation, a single precision step is specified. With a large precision step (say 8), a value is indexed in fewer terms (8) but the number of terms for a range can be large. With a small precision step (say 2), the number of terms for a range is smaller but a value is indexed in more terms (32). We want to add an option that different precision steps can be set for different precisions. An expert can use this option to keep the number of terms for a range small and at the same time index a value in a small number of terms. See the discussion in LUCENE-1470 that results in this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-1541) Trie range - make trie range indexing more flexible
[ https://issues.apache.org/jira/browse/LUCENE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1541: -- Attachment: LUCENE-1541.patch Updated patch (removed the API change in RangeBuilder), as not related to this issue. This patch also restores the original trieCodeLong/Int, that uses the equidistant precision step, so the indexing is faster, because no extra loop needed here. Still missing are tests and javadocs, this still a early version. Trie range - make trie range indexing more flexible --- Key: LUCENE-1541 URL: https://issues.apache.org/jira/browse/LUCENE-1541 Project: Lucene - Java Issue Type: Improvement Components: contrib/* Affects Versions: 2.9 Reporter: Ning Li Assignee: Uwe Schindler Priority: Minor Fix For: 2.9 Attachments: LUCENE-1541.patch, LUCENE-1541.patch In the current trie range implementation, a single precision step is specified. With a large precision step (say 8), a value is indexed in fewer terms (8) but the number of terms for a range can be large. With a small precision step (say 2), the number of terms for a range is smaller but a value is indexed in more terms (32). We want to add an option that different precision steps can be set for different precisions. An expert can use this option to keep the number of terms for a range small and at the same time index a value in a small number of terms. See the discussion in LUCENE-1470 that results in this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-1541) Trie range - make trie range indexing more flexible
[ https://issues.apache.org/jira/browse/LUCENE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1541: -- Attachment: LUCENE-1541.patch A first patch, completely untested: - Javadocs need to be updated - Tests with non-equidistant precision steps must be added - Warning: Method signatures of RangeBuilders changed (order and contents, but not types!!!) - Maybe additional shortcuts in RangeFilters needed (the expert ctor now takes field[] and precisionSteps[]) Does this look like an API, that may work for you? Currently I am not so happy with the additional loop that determines the length of the trie array (in trieCodeLong/Int) and the additional array allocations needed. Trie range - make trie range indexing more flexible --- Key: LUCENE-1541 URL: https://issues.apache.org/jira/browse/LUCENE-1541 Project: Lucene - Java Issue Type: Improvement Components: contrib/* Reporter: Ning Li Assignee: Uwe Schindler Priority: Minor Attachments: LUCENE-1541.patch In the current trie range implementation, a single precision step is specified. With a large precision step (say 8), a value is indexed in fewer terms (8) but the number of terms for a range can be large. With a small precision step (say 2), the number of terms for a range is smaller but a value is indexed in more terms (32). We want to add an option that different precision steps can be set for different precisions. An expert can use this option to keep the number of terms for a range small and at the same time index a value in a small number of terms. See the discussion in LUCENE-1470 that results in this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
