On 14 January 2013 17:28, Jens Grivolla wrote:
> On 01/14/2013 12:50 PM, Gora Mohanty wrote:
[...]
>> Doh! You are right, of course. Brainfart from my side.
>
>
> Ok, I was starting to wonder if I was the one missing something. Re-reading
> what I wrote I see I may have sounded a bit rude, that wa
On 01/14/2013 12:50 PM, Gora Mohanty wrote:
On 14 January 2013 16:59, Jens Grivolla wrote:
[...]
Then please show me the query to find users that are fluent in spanish and
english. Bonus points if you manage to not retrieve the same user several
times. (Hint, your schema stores only one languag
On 14 January 2013 16:59, Jens Grivolla wrote:
[...]
> Then please show me the query to find users that are fluent in spanish and
> english. Bonus points if you manage to not retrieve the same user several
> times. (Hint, your schema stores only one language skill per row).
Doh! You are right, of
On 01/11/2013 06:14 PM, Gora Mohanty wrote:
On 11 January 2013 22:30, Jens Grivolla wrote:
[...]
Actually, that is what you would get when doing a join in an RDBMS, the
cross-product of your tables. This is NOT AT ALL what you typically do in Solr.
Best start the other way around, think of So
On 11 January 2013 22:30, Jens Grivolla wrote:
[...]
> Actually, that is what you would get when doing a join in an RDBMS, the
> cross-product of your tables. This is NOT AT ALL what you typically do in
> Solr.
>
> Best start the other way around, think of Solr as a retrieval system, not a
> st
On 01/11/2013 05:23 PM, Gora Mohanty wrote:
You are still thinking of Solr as a RDBMS, where you should not
be. In your case, it is easiest to flatten out the data. This increases
the size of the index, but that should not really be of concern. As
your courses and languages tables are connected o
On 11 January 2013 21:13, Niklas Langvig wrote:
> It sounds good not to use more than one core, for sure I do not want to over
> complicate this.
[...]
Yes, not only are multiple cores unnecessarily complicated here,
your searches will also be be less complex, and faster.
> Both table courses a
On 11 January 2013 19:57, Niklas Langvig wrote:
> Ahh sorry,
> Now I understand,
> Ok seems like a good solution, I just know need to understand how to query
> multiple cores now :)
There is no need to use multiple cores in your setup. Going
back to your original problem statement, it can easily
xample has one table "user" and I have many tables that
> > connects to one user and that is what I'm unsure how how to do.
> >
> > /Niklas
> >
> >
> > -Ursprungligt meddelande-----
> > Från: Dariusz Borowski [mailto:darius...@gmail.com]
&
ure how how to do.
>
> /Niklas
>
>
> -Ursprungligt meddelande-
> Från: Dariusz Borowski [mailto:darius...@gmail.com]
> Skickat: den 11 januari 2013 14:56
> Till: solr-user@lucene.apache.org
> Ämne: Re: configuring schema to match database
>
> Hi Niklas,
>
> Maybe t
Hi Niklas,
Maybe this link helps:
http://www.coderthing.com/solr-with-multicore-and-database-hook-part-1/
D.
On Fri, Jan 11, 2013 at 2:19 PM, Niklas Langvig <
niklas.lang...@globesoft.com> wrote:
> Hi!
> I'm quite new to solr and trying to understand how to create a schema from
> how our pos
11 matches
Mail list logo
