I see. You can create a JIRA and submit patch and see if committers agree
or have different opinion/suggestion.
Thanks,
Susheel
On Fri, Jun 2, 2017 at 10:01 AM, Sergio García Maroto
wrote:
> You are right about that but in some cases I may need to reindex my data
> and wanted to avoid deleting
You are right about that but in some cases I may need to reindex my data
and wanted to avoid deleting the full index so
I can still server queries. I thought reindexing same version would be
handy or at least to have the flexibility.
On 2 June 2017 at 14:53, Susheel Kumar wrote:
> I see the diff
I see the difference now between using _version_ vs custom versionField.
Both seems to behave differently. The _version_ field if used allows same
version to be updated and that's the perception I had in mind for custom
versionField.
My question is why do you want to update the document if same v
Just to confirm again before go too far, are you able to execute these
examples and see same output given under "Optimistic Concurrency".
https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents#UpdatingPartsofDocuments-In-PlaceUpdates
Let me know which example you fail to ge
I had a look to the source code and I see
DocBasedVersionConstraintsProcessorFactory
if (0 < ((Comparable)newUserVersion).compareTo((Comparable)
oldUserVersion)) {
// log.info("VERSION returning true (proceed with update)" );
return true;
}
I can't find a way of overwriting sa
I am using 6.1.0.
I tried with two different field types, long and date.
I am using this configuration on the solrconfig.xml
false
UpdatedDateSD
i had a look to the wiki page and it says
https://cwiki.apache.org/confluence/display/solr/Upda
Which version of solr are you using? I tested in 6.0 and if I supply same
version, it overwrite/update the document exactly as per the wiki
documentation.
Thanks,
Susheel
On Thu, Jun 1, 2017 at 7:57 AM, marotosg wrote:
> Thanks a lot Susheel.
> I see this is actually what I need. I have been t
Thanks a lot Susheel.
I see this is actually what I need. I have been testing it and notice the
value of the field has to be always greater for a new document to get
indexed. if you send the same version number it doesn't work.
Is it possible somehow to overwrite documents with the same version?
"Document Centric Versioning Constraints" is what you are looking for if
you want this to handled in Solr
https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents
--
Susheel
On Wed, May 31, 2017 at 6:46 AM, marotosg wrote:
> Hi all.
>
> I need to implement an indexation sol
Hi all.
I need to implement an indexation solution where my Solr index doesn't get a
wrong version.
Due to the fact I have many version for the same entity In some cases my
client may end up indexing an earlier version of my entity after a newer
one.
I was wondering if I can use the _version_ fie
10 matches
Mail list logo
