Gerald:
Here's the place to start: http://wiki.apache.org/solr/HowToContribute
But the basic setup is
1> create a JIRA login (anyone can)
2> create a JIRA if one doesn't exist
3> generate the patch. From your root level (the one that contains "solr"
and "lucene" dirs) and "svn diff > SOLR-###.patc
Mikhail-
Let me know how to contribute a test case and I will put it on my to do
list.
When your many-to-many BlockJoin solution matures I would love to see it.
Thanks.
-Gerald
On Tue, Nov 13, 2012 at 11:52 PM, Mikhail Khludnev <
mkhlud...@griddynamics.com> wrote:
> Gerald,
> Nice to hear the
Gerald,
Nice to hear the the your problem is solved. Can you contribute a test case
to reproduce this issue?
FWIW, my team successfully deals with Many-to-Many in BlockJoin. It works,
but solution is a little bit immature yet.
On Wed, Nov 14, 2012 at 5:59 AM, Gerald Blanck <
gerald.bla...@barome
Thank you Mikhail. Unfortunately BlockJoinQuery is not an option we can
leverage.
- We have modeled our document types as different indexes/cores.
- Our relationships which we are attempting to join across are not
single-parent to many-children relationships. They are in fact many to
many.
- Add
Please find reference materials
http://blog.mikemccandless.com/2012/01/searching-relational-content-with.html
http://blog.griddynamics.com/2012/08/block-join-query-performs.html
On Tue, Nov 13, 2012 at 3:25 PM, Gerald Blanck <
gerald.bla...@barometerit.com> wrote:
> Thank you. I've not heard
Gerald,
I wonder if you tried to approach BlockJoin for your problem? Can you
afford less frequent updates?
On Wed, Nov 7, 2012 at 5:40 PM, Gerald Blanck wrote:
> Thank you Erick for your reply. I understand that search is not an RDBMS.
> Yes, we do have a huge combinatorial explosion if we
Thank you Erick for your reply. I understand that search is not an RDBMS.
Yes, we do have a huge combinatorial explosion if we de-normalize and
duplicate data. In fact, I believe our use case is exactly what the Solr
developers were trying to solve with the addition of the Join query. And
while
I'm going to go a bit sideways on you, partly because I can't answer the
question ...
But, every time I see someone doing what looks like substituting "core" for
"table" and
then trying to use Solr like a DB, I get on my soap-box and preach..
In this case, consider de-normalizing your DB so y
At a high level, I have a need to be able to execute a query that joins
across cores, and that query during its joining may join back to the
originating core.
Example:
Find all Books written by an Author who has written a best selling Book.
In Solr query syntax
A) against the book core - bestsell
