Hi Kevin,
I think you made OS06Y the uniqueKey, right?
So, in entity 1 you specify values for it, but in entity 2 you do so as
well.
I am not absolutely sure about this, but: It seems like your two entities
create two documents and the second will overwrite the first.
Have a look at this page:
,it may met performance issue.
-Original Message-
From: Em [mailto:mailformailingli...@yahoo.de]
Sent: Thursday, April 21, 2011 4:38 PM
To: solr-user@lucene.apache.org
Subject: Re: The issue of import data from database using Solr DIH
Hi Kevin,
I think you made OS06Y the uniqueKey, right
Not sure I understood you correct:
You expect that OS06Y stores *two* different performanceIds? One from table1
and the other from table2?
I think this may be a problem.
If both OS06Y-keys are equal, than you can use the syntax as mentioned in
the wiki without any problems. You just have to
: RE: The issue of import data from database using Solr DIH
Not sure I understood you correct:
You expect that OS06Y stores *two* different performanceIds? One from
table1
and the other from table2?
I think this may be a problem.
If both OS06Y-keys are equal, than you can use the syntax
What you want to do is something like a left outer join, isn't it ?
something like : select table2.OS06Y, f1,f2,f3,f4,f5 from table2 left outer
join table1 on table2.OS06Y = table1.OS06Y where ...
could you prepare a view in your RDBMS ? That could be another solution ?
Ludovic.
-
Jouve
As Iboutrus mentioned, if you can summarize it in a query, than yes, Solr can
handle it.
Make a step backward: Do not think of Solr. Write a query (one! query) that
shows exactly the output you exepct. Afterwards, implement this query as a
source for DIH.
Regards,
Em
--
View this message in
.
-Original Message-
From: lboutros [mailto:boutr...@gmail.com]
Sent: Thursday, April 21, 2011 5:25 PM
To: solr-user@lucene.apache.org
Subject: RE: The issue of import data from database using Solr DIH
What you want to do is something like a left outer join, isn't it ?
something like : select
