lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noble Paul നോബിള്‍ नोब्ळ् <noble.p...@corp.aol.com>
Subject Re: Data import problem with child entity from different database
Date Fri, 13 Nov 2009 11:17:45 GMT
no obvious issues.
you may post your entire data-config.xml

do w/o CachedSqlEntityProcessor first and then apply that later


On Fri, Nov 13, 2009 at 4:38 PM, Andrew Clegg <andrew.clegg@gmail.com> wrote:
>
> Morning all,
>
> I'm having problems with joining child a child entity from one database to a
> parent from another...
>
> My entity definitions look like this (names changed for brevity):
>
> <entity name="parent" dataSource="db1" query="select a, b, c from
> parent_table">
>
>  <entity name="child" dataSource="db2" onError="continue" query="select c,
> d from child_table where c = '${parent.c}'" />
>
> </entity>
>
> c is getting indexed fine (it's stored, I can see field 'c' in the search
> results) but child.d isn't. I know the child table has data for the
> corresponding parent rows, and I've even watched the SQL queries against the
> child table appearing in Oracle's sqldeveloper as the DataImportHandler
> runs. But no content for child.d gets into the index.
>
> My schema contains a definition for a field called d like so:
>
> <field name="d" type="keywords_ids" indexed="true" stored="true"
> multiValued="true" termVectors="true" />
>
> (keywords_ids is a conservatively-analyzed text type which has worked fine
> in other contexts.)
>
> Two things occur to me.
>
> 1. db1 is PostgreSQL and db2 is Oracle, although the d field in both tables
> is just a char(4), nothing fancy. Could something weird with character
> encodings be happening?
>
> 2. d isn't a primary key in either parent or child, but this shouldn't
> matter should it?
>
> Additional data points -- I also tried using the CachedSqlEntityProcessor to
> do in-memory table caching of child, but it didn't work then either. I got a
> lot of error messages like this:
>
> No value available for the cache key : d in the entity : child
>
> If anyone knows whether this is a known limitation (if so I can work round
> it), or an unexpected case (if so I'll file a bug report), please shout. I'm
> using 1.4.
>
> Yet again, many thanks :-)
>
> Andrew.
>
> --
> View this message in context: http://old.nabble.com/Data-import-problem-with-child-entity-from-different-database-tp26334948p26334948.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>



-- 
-----------------------------------------------------
Noble Paul | Principal Engineer| AOL | http://aol.com

Mime
View raw message