Hello
In my mapping I have some String values that I need to use for text
matching as well as for sorting.  To support this, I use a multi-field with
two different versions of the field using two different analyzers.  To
sort, I have a keyword-lowercasing analyzer.  For the text search I'm using
the included snowball analyzer.
This works fine for a normal, top-level field.  However, for my nested
fields using this pattern, only the first/primary field type will allow
searching.  The output from tests using the other always returns a null
value.
I'm assuming it's somehow related to the pathing (mixing nested pathing
notation with multi-field notation), but I'm not sure.  Does anyone have
any insight?  I have a full working example herehttp://sense.qbox.io/gist/92524e522f5096f98c59cc6f2da7ffa213433536
.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/cd3d5501-a34a-4a83-88b6-d5165cec77f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
             
            
              
              
              
            
            
           
          
            
            
              On Thursday, April 24, 2014 8:12:26 AM UTC-4, Jonathan Foy wrote:
Hello
In my mapping I have some String values that I need to use for text
matching as well as for sorting.  To support this, I use a multi-field with
two different versions of the field using two different analyzers.  To
sort, I have a keyword-lowercasing analyzer.  For the text search I'm using
the included snowball analyzer.
This works fine for a normal, top-level field.  However, for my nested
fields using this pattern, only the first/primary field type will allow
searching.  The output from tests using the other always returns a null
value.
I'm assuming it's somehow related to the pathing (mixing nested pathing
notation with multi-field notation), but I'm not sure.  Does anyone have
any insight?  I have a full working example herehttp://sense.qbox.io/gist/92524e522f5096f98c59cc6f2da7ffa213433536
.
Received help on SOhttp://stackoverflow.com/questions/23255991/elasticsearch-sorting-by-a-nested-multi-field#23275061,
I was missing the "nested_path" parameter in the sort definition.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/284b0c4a-d570-4e07-9201-c30a38f4e63d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.