Hey Gunaranjan,
I have the same scenario as you.
A lucene index is denormalized. It should not contain entity relationship.
When I need to do something like you are doing, I group the related values
in one field.
Let's say we have 2 credit cards. the first has id 30459673 and taxes at
1.5%/month
Paul
Its not just about merging the fields or resource usage. If you look
at the scenario below, the issue is that it mixes up my fields
(shipping and billing address) for instance. I can't merge them and
still keep the 'distinction' for search.Your case is a
'generalization' field.
Thanks
Much appreciate the guidance. I think I will go with the single field
approach for now. Also will take a look at the URL below and come
back if I have any ideas.
Guna
On Jan 25, 2009, at 12:49 AM, Shalin Shekhar Mangar wrote:
On Sun, Jan 25, 2009 at 2:05 PM, Gunaranjan Chandraraju
Guna,
it's really really normal to duplicate stuffs to be merged into a field.
We do this all the time, for example to have a field "text-in-any-
language" while a field "text-in-english" is also there and the
queries boost matches in text-in-any-language less than text-in-
english (if user
On Sun, Jan 25, 2009 at 2:05 PM, Gunaranjan Chandraraju <
chandrar...@apple.com> wrote:
> Thanks
> This sounds redundant to me - to store the fields separately and then
> concat all of them to one copy field again.
>
Sometimes that may be the only way. For example, if you want to facet on
some of
Thanks
This sounds redundant to me - to store the fields separately and then
concat all of them to one copy field again.
My XML is like this
I am currently using XPATH or XSL to separate them into individual
indexed fields like: address_state_1, address_type_1 etc. in SOLR.
From what you
for searching you need to put them in a single field . use
in schema.xml to achieve that
On Sun, Jan 25, 2009 at 7:39 AM, Gunaranjan Chandraraju
wrote:
> I make this approach work with XPATH and XSL. However, this approach
> creates multiple fields of like this
>
> address_state_1
> address_st
I make this approach work with XPATH and XSL. However, this approach
creates multiple fields of like this
address_state_1
address_state_2
...
address_state_10
and
credit_card_1
credit_card_2
credit_card_3
How do I search for a credit_card.The query syntax does not seem
to support wi
Hi Fergus,
XPathEntityprocessor can read multivalued fields easily
eg
***change**
In this case all address_street,address_state,address_type will be
returned as s
nesting of an XPathEntityProcessor into another XPathEntityProcessor
is possible only if a field in an xml is a filename/url .
what is the purpose of nesting like this?
is it because you have multiple addresses? the possible solutions are
discussed elsewhere in this thread
On Sat, Jan 24, 2009 at
Hello,
I am also a newbie and was wanting to do almost the exact same thing.
I was planning on doing the equivalent of:-
***change**
Yes Solr does. But DataImportHandler with the 1.3 release does not support
it.
However, you can use the trunk data import handler jar with Solr 1.3 if you
do not feel comfortable using Solr 1.4 trunk.
On Fri, Jan 23, 2009 at 1:36 PM, Gunaranjan Chandraraju <
chandrar...@apple.com> wrote:
>
> I t
I thought 1.3 supported dynamic fields in schema.xml?
Guna
On Jan 22, 2009, at 11:54 PM, Shalin Shekhar Mangar wrote:
Oops, one more gotcha. The dynamic field support is only in 1.4 trunk.
On Fri, Jan 23, 2009 at 1:24 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
On Fri, Jan 2
I thought 1.3 supported dynamic fields in schema.xml?
Guna
On Jan 22, 2009, at 11:54 PM, Shalin Shekhar Mangar wrote:
Oops, one more gotcha. The dynamic field support is only in 1.4 trunk.
On Fri, Jan 23, 2009 at 1:24 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
On Fri, Jan 2
Oops, one more gotcha. The dynamic field support is only in 1.4 trunk.
On Fri, Jan 23, 2009 at 1:24 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> On Fri, Jan 23, 2009 at 1:08 PM, Gunaranjan Chandraraju <
> chandrar...@apple.com> wrote:
>
>>
>>
>>
>>
>>
>>
>>
>>
>> I h
On Fri, Jan 23, 2009 at 1:08 PM, Gunaranjan Chandraraju <
chandrar...@apple.com> wrote:
>
>
>
>
>
>
>
>
> I have setup my DIH to treat these as entities as below
>
>
>
>
> baseDir="***"
> fileName=".*xml"
> rootEntity="false"
>
Hi
I may be completely off on this being new to SOLR but I am not sure
how to index related groups of fields in a document and preserver
their 'grouping'. I would appreciate any help on this.Detailed
description of the problem below.
I am trying to index an entity that can have mult
17 matches
Mail list logo