[jira] [Updated] (SOLR-11841) Removing values from a multivalued EnumField by Atomic Update does not work when using XML as codec
[ https://issues.apache.org/jira/browse/SOLR-11841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Wöckinger updated SOLR-11841: Affects Version/s: 6.6.5 > Removing values from a multivalued EnumField by Atomic Update does not work > when using XML as codec > --- > > Key: SOLR-11841 > URL: https://issues.apache.org/jira/browse/SOLR-11841 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Server, UpdateRequestProcessors >Affects Versions: 6.6.2, 6.6.5, 7.6, 7.7, 7.7.1, 8.0 > Environment: EmbeddedSolrServer, HttpSolrClient when using > RequestWriter instead of BinaryRequestWriter >Reporter: Thomas Wöckinger >Priority: Major > Labels: pull-request-available, ready-to-commit, test > Time Spent: 20m > Remaining Estimate: 0h > > If XMLLoader is used to build SolrInputDocuments Enum values are treated as > String values and not as EnumFieldValue like it is done by the binary codec. > So the doRemove call of AtomicUpdateDocumentMerger will get String values > which does not match any EnumFieldValue from the existingField values. > The behaviour can be tested easily with the EmbeddedSolrServer because it > uses the XML codec to convert the SolrRequest. > Just create a multivalued EnumField add some values and try to remove some > with > atomic update calls. > The values will remain unchanged. -- 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] [Updated] (SOLR-11841) Removing values from a multivalued EnumField by Atomic Update does not work when using XML as codec
[ https://issues.apache.org/jira/browse/SOLR-11841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Wöckinger updated SOLR-11841: Affects Version/s: 7.6 7.7 7.7.1 8.0 > Removing values from a multivalued EnumField by Atomic Update does not work > when using XML as codec > --- > > Key: SOLR-11841 > URL: https://issues.apache.org/jira/browse/SOLR-11841 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Server, UpdateRequestProcessors >Affects Versions: 6.6.2, 7.6, 7.7, 7.7.1, 8.0 > Environment: EmbeddedSolrServer, HttpSolrClient when using > RequestWriter instead of BinaryRequestWriter >Reporter: Thomas Wöckinger >Priority: Major > Labels: pull-request-available, ready-to-commit, test > Time Spent: 20m > Remaining Estimate: 0h > > If XMLLoader is used to build SolrInputDocuments Enum values are treated as > String values and not as EnumFieldValue like it is done by the binary codec. > So the doRemove call of AtomicUpdateDocumentMerger will get String values > which does not match any EnumFieldValue from the existingField values. > The behaviour can be tested easily with the EmbeddedSolrServer because it > uses the XML codec to convert the SolrRequest. > Just create a multivalued EnumField add some values and try to remove some > with > atomic update calls. > The values will remain unchanged. -- 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] [Updated] (SOLR-11841) Removing values from a multivalued EnumField by Atomic Update does not work when using XML as codec
[ https://issues.apache.org/jira/browse/SOLR-11841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Wöckinger updated SOLR-11841: Labels: pull-request-available ready-to-commit test (was: pull-request-available test) > Removing values from a multivalued EnumField by Atomic Update does not work > when using XML as codec > --- > > Key: SOLR-11841 > URL: https://issues.apache.org/jira/browse/SOLR-11841 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Server, UpdateRequestProcessors >Affects Versions: 6.6.2 > Environment: EmbeddedSolrServer, HttpSolrClient when using > RequestWriter instead of BinaryRequestWriter >Reporter: Thomas Wöckinger >Priority: Major > Labels: pull-request-available, ready-to-commit, test > Time Spent: 20m > Remaining Estimate: 0h > > If XMLLoader is used to build SolrInputDocuments Enum values are treated as > String values and not as EnumFieldValue like it is done by the binary codec. > So the doRemove call of AtomicUpdateDocumentMerger will get String values > which does not match any EnumFieldValue from the existingField values. > The behaviour can be tested easily with the EmbeddedSolrServer because it > uses the XML codec to convert the SolrRequest. > Just create a multivalued EnumField add some values and try to remove some > with > atomic update calls. > The values will remain unchanged. -- 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
