You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sdap.apache.org by "Frank Greguska (JIRA)" <ji...@apache.org> on 2019/02/12 21:29:00 UTC
[jira] [Updated] (SDAP-167) Make shard key configureable
[ https://issues.apache.org/jira/browse/SDAP-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Greguska updated SDAP-167:
--------------------------------
Description:
Currently the dataset name is used as the prefix for the compositeId used for routing
[https://lucene.apache.org/solr/guide/7_4/shards-and-indexing-data-in-solrcloud.html#document-routing]
This is done in the SolrStore writer
[https://github.com/apache/incubator-sdap-ningester/blob/12e60f2c0f11be33026808d98623d5cbe136179d/src/main/java/org/apache/sdap/ningester/writer/SolrStore.java#L94]
This might not be appropriate for every case (for example, if only one dataset is ever going to be ingested). It would be nice to make this configureable.
Also need to expose the key as a configuration option for SolrProxy in data-access during query time (also, 'shard_keys' needs to be changed to '_route_').
https://github.com/apache/incubator-sdap-nexus/blob/master/data-access/nexustiles/dao/SolrProxy.pyx#L631
was:
Currently the dataset name is used as the prefix for the compositeId used for routing
[https://lucene.apache.org/solr/guide/7_4/shards-and-indexing-data-in-solrcloud.html#document-routing]
This is done in the SolrStore writer
[https://github.com/apache/incubator-sdap-ningester/blob/12e60f2c0f11be33026808d98623d5cbe136179d/src/main/java/org/apache/sdap/ningester/writer/SolrStore.java#L94]
This might not be appropriate for every case (for example, if only one dataset is ever going to be ingested). It would be nice to make this configureable.
> Make shard key configureable
> ----------------------------
>
> Key: SDAP-167
> URL: https://issues.apache.org/jira/browse/SDAP-167
> Project: Apache Science Data Analytics Platform
> Issue Type: Improvement
> Components: nexus
> Reporter: Frank Greguska
> Priority: Minor
> Fix For: 1.1
>
>
> Currently the dataset name is used as the prefix for the compositeId used for routing
> [https://lucene.apache.org/solr/guide/7_4/shards-and-indexing-data-in-solrcloud.html#document-routing]
> This is done in the SolrStore writer
> [https://github.com/apache/incubator-sdap-ningester/blob/12e60f2c0f11be33026808d98623d5cbe136179d/src/main/java/org/apache/sdap/ningester/writer/SolrStore.java#L94]
>
> This might not be appropriate for every case (for example, if only one dataset is ever going to be ingested). It would be nice to make this configureable.
>
> Also need to expose the key as a configuration option for SolrProxy in data-access during query time (also, 'shard_keys' needs to be changed to '_route_').
> https://github.com/apache/incubator-sdap-nexus/blob/master/data-access/nexustiles/dao/SolrProxy.pyx#L631
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)