[
https://issues.apache.org/jira/browse/SOLR-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300551#comment-15300551
]
Ishan Chattopadhyaya edited comment on SOLR-5944 at 5/25/16 6:10 PM:
---------------------------------------------------------------------
Attaching fresh patch from the
https://github.com/chatman/lucene-solr/tree/solr_5944 branch.
I've added a test based on SolrTestCaseJ4, which fails, despite suppressing the
Lucene54 and Memory codecs. I am now trying to reproduce this issue in a
LuceneTestCase test.
https://github.com/chatman/lucene-solr/commit/b80be98d9e1a98b97bee670a2d775f6acc2182c7
Reproduce:
{code}
-ea -Dtests.seed=1D9D6101E3D231FF -Dtests.verbose=true
-Dtestcase=TestInPlaceUpdate
{code}
Couple things I noticed that: (a) this happens when Compressing codec is used,
along with (b) the "crazy" value of max buffered docs is used as per this part
from the randomization in LuceneTestCase.java
{code}
if (r.nextBoolean()) {
if (rarely(r)) {
// crazy value
c.setMaxBufferedDocs(TestUtil.nextInt(r, 2, 15));
} else {
// reasonable value
c.setMaxBufferedDocs(TestUtil.nextInt(r, 16, 1000));
}
}
{code}
However, I can't reproduce the failure based on just those two factors; there
must be something else that I'm unable to pinpoint.
was (Author: ichattopadhyaya):
Attaching fresh patch from the
https://github.com/chatman/lucene-solr/tree/solr_5944 branch.
I've added a test based on SolrTestCaseJ4, which fails, despite suppressing the
Lucene54 and Memory codecs. I am now trying to reproduce this issue in a
LuceneTestCase test.
https://github.com/chatman/lucene-solr/commit/b80be98d9e1a98b97bee670a2d775f6acc2182c7
Reproduce:
{code}
-ea -Dtests.seed=1D9D6101E3D231FF -Dtests.verbose=true
-Dtestcase=TestInPlaceUpdate
{code}
Couple things I noticed that this happens when Compressing codec is used, along
with the "crazy" value of max buffered docs is used as per this part from the
randomization in LuceneTestCase.java
{code}
if (r.nextBoolean()) {
if (rarely(r)) {
// crazy value
c.setMaxBufferedDocs(TestUtil.nextInt(r, 2, 15));
} else {
// reasonable value
c.setMaxBufferedDocs(TestUtil.nextInt(r, 16, 1000));
}
}
{code}
However, I can't reproduce the failure based on just those two factors; there
must be something else that I'm unable to pinpoint.
> Support updates of numeric DocValues
> ------------------------------------
>
> Key: SOLR-5944
> URL: https://issues.apache.org/jira/browse/SOLR-5944
> Project: Solr
> Issue Type: New Feature
> Reporter: Ishan Chattopadhyaya
> Assignee: Shalin Shekhar Mangar
> Attachments: DUP.patch, SOLR-5944.patch, SOLR-5944.patch,
> SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch,
> SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch,
> SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch,
> SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch,
> SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch,
> SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch, SOLR-5944.patch,
> SOLR-5944.patch,
> TestStressInPlaceUpdates.eb044ac71.beast-167-failure.stdout.txt,
> TestStressInPlaceUpdates.eb044ac71.beast-587-failure.stdout.txt,
> TestStressInPlaceUpdates.eb044ac71.failures.tar.gz,
> hoss.62D328FA1DEA57FD.fail.txt, hoss.62D328FA1DEA57FD.fail2.txt,
> hoss.62D328FA1DEA57FD.fail3.txt, hoss.D768DD9443A98DC.fail.txt,
> hoss.D768DD9443A98DC.pass.txt
>
>
> LUCENE-5189 introduced support for updates to numeric docvalues. It would be
> really nice to have Solr support this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
