[
https://issues.apache.org/jira/browse/SOLR-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-7404:
---------------------------
Attachment: SOLR-7404.patch
bq. Also, after running the above, POSTing books.csv to the gettingstarted
collection seems to show some versions:
Yeah ... it's bat-shit crazy.
I haven't even begun to try and make sense of what's going on here, but my
starting point (attached patch) was trying to add some sanity checks to the
SolrTestCaseJ4 convinience methods that depend on this feature.
unfortunately i clearly don't understand what the "normal" behavior is suppose
to be in all cases, since i'm seeing that deletes frequently don't include a
version, and when they do it's frequently negative.
> versions=true not working with data_driven_schema_configs ?
> -----------------------------------------------------------
>
> Key: SOLR-7404
> URL: https://issues.apache.org/jira/browse/SOLR-7404
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Attachments: SOLR-7404.patch
>
>
> i haven't dug into this yet, but i've confirmed (at least with Solr 5.1) that
> something about using the data_driven_schema_configs prevents the
> {{versions=true}} update request param from working -- every doc just returns
> "0" as the new version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
