[
https://issues.apache.org/jira/browse/SOLR-12298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470418#comment-16470418
]
Alexandre Rafalovitch commented on SOLR-12298:
----------------------------------------------
{quote}It would be nice if you could just index JSON as is, like you can in
elastic search, moving the responsibility from the user to Solr itself.
{quote}
So, it is been a couple of years since I looked at Elasticsearch, but there
were some things about their "you can" implementation:
# They only accepted JSON, so did not have to deal with content coming in
potentially in different formats (e.g. XML)
# To *update* the document, they had to retrieve the original json from the
\_source_ field, modify it, rewrite it (losing all original
formatting/comments/etc) and reindex from scratch.
# That \_source_ field was considered a bad idea for the production as it was
very performance-limiting (just like any large stored field would be)
# That, AFAIK, is how they remembered whether the original field was
single-valued or multi-valued, because internally they would have everything as
magically multivalued
Perhaps somebody who has a recent ES installation can do this quick test on
what happens now, but - regardless - I think those original lessons may still
be something to consider as we are planning Solr changes.
> Index Full nested document Hierarchy For Queries (umbrella issue)
> -----------------------------------------------------------------
>
> Key: SOLR-12298
> URL: https://issues.apache.org/jira/browse/SOLR-12298
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: mosh
> Priority: Major
>
> Solr ought to have the ability to index deeply nested objects, while storing
> the original document hierarchy.
> Currently the client has to index the child document's full path and level
> to manually reconstruct the original document structure, since the children
> are flattened and returned in the reserved "__childDocuments__" key.
> Ideally you could index a nested document, having Solr transparently add the
> required fields while providing a document transformer to rebuild the
> original document's hierarchy.
>
> This issue is an umbrella issue for the particular tasks that will make it
> all happen – either subtasks or issue linking.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
