[
https://issues.apache.org/jira/browse/SOLR-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217295#comment-14217295
]
Alexandre Rafalovitch commented on SOLR-6633:
---------------------------------------------
Is this somehow superseding the behavior in SOLR-6304 and
http://lucidworks.com/blog/indexing-custom-json-data/ ? I mean the field
extraction code can already do ID mapping by specifying an appropriate path,
right? And for 'df', would you need to specify it as a param (like in the
example 4 in the article)?
And I am still trying to wrap my head about the use case. I don't expect users
not to want to configure *anything*. At least the dates would need to be
parsed/detected. And, usually, after the initial dump, the users go back and
start adding specific definitions field by field, type by type (and reindex).
Is that part of this scenario as well?
P.s. I know Solr cannot clone Elasticsearch. I was just making sure that we are
not somehow missing Solr-specifics by assuming Elasticsearch like behavior.
Perhaps having the field also called *_all* was what confused me.
> let /update/json/docs store the source json as well
> ---------------------------------------------------
>
> Key: SOLR-6633
> URL: https://issues.apache.org/jira/browse/SOLR-6633
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
> Assignee: Noble Paul
> Labels: EaseOfUse
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-6633.patch, SOLR-6633.patch
>
>
> it is a common requirement to store the entire JSON as a field in Solr.
> we can have a extra param srcField=field_name to specify the field name
> the /update/json/docs is only useful when all the json fields are predefined
> or in schemaless mode.
> The better option would be to store the content in a store only field and
> index the data in another field in other modes
> the relevant section in solrconfig.xml
> {code:xml}
> <initParams path="/update/json/docs">
> <lst name="defaults">
> <!--this ensures that the entire json doc will be stored verbatim into
> one field-->
> <str name="srcField">_src</str>
> <!--This means a the uniqueKeyField will be extracted from the fields
> and
> all fields go into the 'df' field. In this config df is already
> configured to be 'text'
> -->
> <str name="mapUniqueKeyOnly">true</str>
> <str name="df">text</str>
> </lst>
> </initParams>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
