[
https://issues.apache.org/jira/browse/SOLR-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412124#comment-15412124
]
Ishan Chattopadhyaya commented on SOLR-5944:
--------------------------------------------
Regarding LUCENE-7344,
{quote}
We still need some sort of solution to this problem – the suggested
requirement/documentation workarround suggested by McCandless in that issue
doesn't really fit with how all work on this jira to date has kept the the
decision of when/if to do an "in-place" update a low level implementation
detail .... that would have to radically change if we wanted to "pass the buck"
up to the user to say "you an't use DBQ on a docvalue field that you also use
for in place updates"
so what's our Solr solution / workaround? do we have any?
{quote}
I tried to look for a workaround in Solr, but couldn't figure out a viable
workaround. Given that we're looking to have in-place updates replace the
current atomic updates mechanism transparently when certain fields types are
involved (i.e. non-stored, non-indexed, single valued docvalues), LUCENE-7344
is a blocker for that: i.e. if a user updates a dv field, and issues a DBQ
trying to use that updated value without a commit in between, then the DBQ
doesn't actually use the updated value, but uses the older (last committed)
value.
One approach is to not have in-place updates be a transparent replacement to
atomic updates and be enabled or disabled (by default) on certain fields. By
doing this, we can document that enabling in-place updates has the downside
that DBQs on the updated values wouldn't work unless there's an explicit or
auto commit between the update and the dbq.
[~shaie] Would love to hear your thoughts on this, and your suggestions on how
should we go about dealing with LUCENE-7344.
> 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, 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: [email protected]
For additional commands, e-mail: [email protected]
