lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Rafalovitch (JIRA)" <>
Subject [jira] [Commented] (SOLR-4383) DataImportHandler: Semantic inconsistency of column/name attribute
Date Tue, 19 Feb 2013 13:59:13 GMT


Alexandre Rafalovitch commented on SOLR-4383:

This causes further confusion when using variable resolver (Wiki does not help). In the example
below, I have to have non-existant column names and then I have to use _those_ names for my
variable resolution.

    <entity name="vac" 
      query="select * from ALERTS"
      <field column="id" name="ID" />
      <field name="type" column="FAKE" template="vacancy-alert"/>
      <field name="vac_id" column="FAKE2" sourceColName="SUBJECT" regex="^\((.*)\)"/>

      <entity name="vacancy-geocoder"
        query="select LOC from GEOCODE where NAME = '${vac.FAKE2}'"
        <field name="vac_loc" column="LOC" />

> DataImportHandler: Semantic inconsistency of column/name attribute
> ------------------------------------------------------------------
>                 Key: SOLR-4383
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: contrib - DataImportHandler, documentation
>    Affects Versions: 4.1
>            Reporter: Alexandre Rafalovitch
>             Fix For: 5.0
> Different DIH Entity Processor assign different meaning to 'column' attribute. This can
cause serious confusion to beginners but can also lead to extremely hard to troubleshoot subtle

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message