Re: entity name issue

[tjtong]

Hi Em,

Thanks a lot! But it still does not work. Actually my "where" clause in my
query was '${dataimporter.request.clean}' != 'false' and
myschema.table_a.aid=${dataimporter.request.aid}" which I used to pass a
value to the full import process, and it worked without the prefix
"myschema." on sybase database, but did not work on oracle either with or
without the prefix. (It would complain table not existing without the
prefix). 

TJ

--
View this message in context: 
http://lucene.472066.n3.nabble.com/entity-name-issue-tp2843812p2846816.html
Sent from the Solr - User mailing list archive at Nabble.com.

entity name issue

[tjtong]

Hi guys,

I have encountered a problem with entity name, see the data config code
below. the variable '${ea.a_aid}' was always empty. I suspect it is a
namespace issue. Anyone knows how to bypass it? 

This is on oracle database. I had to use the prefix "myschema.", otherwise,
the table name was not recognized. The similar thing worked on database
without adding a prefix to the table names.
Thanks in advance!

  

   

--
View this message in context: 
http://lucene.472066.n3.nabble.com/entity-name-issue-tp2843812p2843812.html
Sent from the Solr - User mailing list archive at Nabble.com.

Why does solr keeps creating connections in full import

[tjtong]

Why does solr keeps creating connections for each table, even though they are
in the same database? This happened in the process of full-import. I used
one table as the root entity, and join the other tables. But solr keeps
creating database connections for each table. Any one has any idea or had
same problem? Thanks.

--
View this message in context: 
http://lucene.472066.n3.nabble.com/Why-does-solr-keeps-creating-connections-in-full-import-tp2790786p2790786.html
Sent from the Solr - User mailing list archive at Nabble.com.