[
https://issues.apache.org/jira/browse/SOLR-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222359#comment-13222359
]
Mark Miller commented on SOLR-3154:
-----------------------------------
The main difficulty here is that to get the readable to indexed id that we
hash, we need the field type and the id field. The id field we can simply have
the user supply - but technically each field type can impl a custom method to
get the indexed id that we hash on. Not sure what we do about this, but
initially I was thinking we could support one or two field types (int, string)
and just copy the (simple) logic for these two types into the server impl. Then
the user would also have to supply the type (int,string) of the id field as
well - though we could default it to what the example schema uses.
> SolrJ CloudServer should be leader and network aware when adding docs
> ---------------------------------------------------------------------
>
> Key: SOLR-3154
> URL: https://issues.apache.org/jira/browse/SOLR-3154
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Grant Ingersoll
> Priority: Minor
> Fix For: 4.0
>
>
> It would be good when indexing if the SolrJ CloudServer was leader aware so
> that we could avoid doing an extra hop for the data. It would also be good
> if one could easily set things up based on data locality principles. This
> might mean that CloudServer is aware of where on the network it is and would
> pick leaders that are as close as possible (i.e. local, perhaps.) This would
> come in to play when working with tools like Hadoop or other grid computing
> frameworks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
