lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mosh (JIRA)" <>
Subject [jira] [Commented] (SOLR-12768) Determine how _nest_path_ should be analyzed to support various use-cases
Date Tue, 01 Jan 2019 15:36:00 GMT


mosh commented on SOLR-12768:

{quote}About the new analysis.... TestChildDocTransformerHierarchy has many test methods that
fail. I have yet to update them to pass. Many fail because of a combination of two factors
(a) they use an experimental syntax for the "childFilter" parameter that is defined in org.apache.solr.response.transform.ChildDocTransformerFactory#processPathHierarchyQueryString{quote}
Opened a new PR including fixes to failing tests in TestChildDocTransformerHierarchy.
I updated theses tests for the new analysis chain.
ChildDocTransformerFactory#processPathHierarchyQueryString now prefixes filters with * when
the path is not absolute(does not start with a '/').

> Determine how _nest_path_ should be analyzed to support various use-cases
> -------------------------------------------------------------------------
>                 Key: SOLR-12768
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Blocker
>             Fix For: master (8.0)
>         Attachments: SOLR-12768.patch
>          Time Spent: 10m
>  Remaining Estimate: 0h
> We know we need {{\_nest\_path\_}} in the schema for the new nested documents support,
and we loosely know what goes in it.  From a DocValues perspective, we've got it down; though
we might tweak it.  From an indexing (text analysis) perspective, we're not quite sure yet,
though we've got a test schema, {{schema-nest.xml}} with a decent shot at it.  Ultimately,
how we index it will depend on the query/filter use-cases we need to support.  So we'll review
some of them here.
> TBD: Not sure if the outcome of this task is just a "decide" or wether we also potentially
add a few tests for some of these cases, and/or if we also add a FieldType to make declaring
it as easy as a one-liner.  A FieldType would have other benefits too once we're ready to
make querying on the path easier.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message