You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Dawid Weiss (JIRA)" <ji...@apache.org> on 2017/01/23 13:54:26 UTC
[jira] [Updated] (SOLR-10012) DIH's XPath processor works
incorrectly for overlapping XPath paths defined as different fields
[ https://issues.apache.org/jira/browse/SOLR-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Weiss updated SOLR-10012:
-------------------------------
Summary: DIH's XPath processor works incorrectly for overlapping XPath paths defined as different fields (was: DIH's XPath processor ignores field matches if parent is 'flattened'?)
> DIH's XPath processor works incorrectly for overlapping XPath paths defined as different fields
> -----------------------------------------------------------------------------------------------
>
> Key: SOLR-10012
> URL: https://issues.apache.org/jira/browse/SOLR-10012
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Dawid Weiss
> Priority: Minor
>
> Reported by a friend --
> {code}
> <dataConfig>
> ...
> <field column="Address" xpath="/records/fullrecord_metadata/addresses/address_name/address_spec/full_address" />
> <field column="AddressALL" xpath="/records/fullrecord_metadata/addresses flatten="true" />
> ...
> </dataConfig>
> {code}
> This definition doesn't seem to be importing anything in {{Address}} field -- everything is consumed by AddressALL.
> I looked briefly at the implementation of {{XPathRecordReader}} and it seems it's greedy with respect to flattened tree nodes, assuming no other field extracts data from subnodes.
> I think this is a bug (or is it by design)?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org