[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506465#comment-16506465
]
ASF subversion and git services commented on SOLR-12378:
Commit 72022c293ef82eb2e69949c803fa7889e070286d in lucene-solr's branch
refs/heads/branch_7_4 from [~ctargett]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=72022c2 ]
SOLR-12378: Ref Guide: reformat parameter list; break up big paragraph; fix
typos
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506463#comment-16506463
]
ASF subversion and git services commented on SOLR-12378:
Commit b47cb38d63d0c9d8518f81a83845ebe61a517ce1 in lucene-solr's branch
refs/heads/branch_7x from [~ctargett]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b47cb38 ]
SOLR-12378: Ref Guide: reformat parameter list; break up big paragraph; fix
typos
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506460#comment-16506460
]
ASF subversion and git services commented on SOLR-12378:
Commit 9b5dd15471a979ef4e5f197c6673e0e324b2f24d in lucene-solr's branch
refs/heads/master from [~ctargett]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9b5dd15 ]
SOLR-12378: Ref Guide: reformat parameter list; break up big paragraph; fix
typos
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488389#comment-16488389
]
ASF subversion and git services commented on SOLR-12378:
Commit 7f0b184c66d501e45f33ae8a52ba4603725d39f0 in lucene-solr's branch
refs/heads/branch_7x from markrmiller
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=7f0b184 ]
SOLR-12378: Support missing versionField on indexed docs in
DocBasedVersionConstraintsURP.
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488026#comment-16488026
]
ASF subversion and git services commented on SOLR-12378:
Commit 48bd259516b8d78c991239fe7cf3340c90f582e5 in lucene-solr's branch
refs/heads/master from markrmiller
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=48bd259 ]
SOLR-12378: Support missing versionField on indexed docs in
DocBasedVersionConstraintsURP.
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487408#comment-16487408
]
Mark Miller commented on SOLR-12378:
+1, I'll make that change and commit.
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487203#comment-16487203
]
Michael Braun commented on SOLR-12378:
--
Just a thought for simplification, instead of creating a new Comparable and
overriding, can the lambda syntax be used, such as userVersions[i] =
(Comparable) o -> -1; ?
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487186#comment-16487186
]
Michael Braun commented on SOLR-12378:
--
Given that it's a config option, this makes sense!
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16485777#comment-16485777
]
Mark Miller commented on SOLR-12378:
Looks like we have doc on this URP in the ref guide - new patch with an entry
for this option.
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484772#comment-16484772
]
Oliver Bates commented on SOLR-12378:
-
Thanks Mark :)
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Assignee: Mark Miller
>Priority: Minor
> Labels: features, patch
> Attachments: SOLR-12378.patch, supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484694#comment-16484694
]
Oliver Bates commented on SOLR-12378:
-
{quote}Did you intentionally mispell an existing comment RE "identiy" ?
{quote}
Lol yeah I'm just here to wreak havoc. Actually that typo existed in an older
version of the file, which my original patch was based on (and I had actually
fixed that typo too!) but I clearly messed something up when I rebased on the
latest** master.
{quote}Can you please update your patch for master? This file was recently
split in two.
{quote}
**Obviously not latest enough.
Sorry about that. [~tomasflobbe] actually mentioned to me a couple days ago
that the files had changed but I didn't get a chance to fix it yet. Will upload
a new patch later today.
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Priority: Minor
> Labels: features, patch
> Attachments: supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484612#comment-16484612
]
David Smiley commented on SOLR-12378:
-
Did you intentionally mispell an existing comment RE "identiy" ?
Can you please update your patch for master? This file was recently split in
two.
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Priority: Minor
> Labels: features, patch
> Attachments: supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482067#comment-16482067
]
Oliver Bates commented on SOLR-12378:
-
You checked out the Jira too quickly! [~dsmiley]
!/jira/images/icons/emoticons/wink.png!
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Priority: Minor
> Labels: features, patch
> Attachments: supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12378) Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482033#comment-16482033
]
David Smiley commented on SOLR-12378:
-
Agreed; this would be cool. Patches welcome :)
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
>Affects Versions: master (8.0)
>Reporter: Oliver Bates
>Priority: Minor
> Labels: features, patch
> Attachments: supportMissingVersionOnOldDocs-v1.patch
>
>
> If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor on
> an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> Reindexing isn't always practical/possible. The proposal here is to have an
> option to allow the existing docs to be missing this field and to simply
> treat those docs as older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
