[
https://issues.apache.org/jira/browse/SOLR-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943401#comment-15943401
]
Shawn Heisey commented on SOLR-7242:
------------------------------------
[~steve_rowe], I am wondering whether the API to change the uniqueKey should
attempt to ensure that the field is suitable. A "force" option may not be a
bad thing to add, to let the user do what they want, even if the software
doesn't think it's a good idea.
One thing that I think would be good to check is to make sure that the new
field isn't using the TextField class. A uniqueKey field that can be analyzed
has the possibility of being unsuitable for that role.
Another thing to check is that the field is entirely comprised of unique
values. If the index is empty, that would qualify. Another check that could
be done: Run an internal facet query on the field and make sure that none of
the counts are more than 1. Because of the nature of facet queries on
high-cardinality fields, that query could run into OOME problems, especially on
distributed cloud indexes with multiple shards per node.
> Schema API: Edit remaining schema elements: Name, Version, Unique Key, and
> Global Similarity
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-7242
> URL: https://issues.apache.org/jira/browse/SOLR-7242
> Project: Solr
> Issue Type: Sub-task
> Components: Schema and Analysis
> Reporter: Steve Rowe
> Assignee: Steve Rowe
>
> We should be able to specify an entire schema via the bulk schema API.
> The bulk schema API should have the following commands in addition to those
> already available/planned:
> # {{set-name}}
> # {{set-version}}
> # {{set-unique-key}}/{{unset-unique-key}}
> # {{set-similarity}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
