Vazquez,
Sorry I don't have an answer but I'd love to know what you need this for :-)
I think the logic is going to have to bleed into your search app. In
short copy field and your app knows which to search in.
lee c
On 30 April 2012 20:41, Erick Erickson wrote:
> OK, I took another look at w
OK, I took another look at what you were trying to
accomplish and, I find the use-case kind of hard to
figure out, but that's my problem .
But it is true that there's really no good way to _change_ the
way the field is analyzed in Solr. Of course since Solr is
built on Lucene, you could to a lot o
Thanks Erick.
I'm not concerned about the logic, all I want to achieve is sometimes
storing/indexing a multi-valued field and sometimes not (same field with
same name) based on some logic. In a transformer I cannot change the
schema dynamically to do that, not that I know of at least.
So if I defin
Your idea of using a Transformer will work just fine, you have a lot more
flexibility in a custom Transformer, see:
http://wiki.apache.org/solr/DIHCustomTransformer
You could also write a custom update handler that examined the
document on the server side and implemented your logic, or even
just a
Thanks for your response.
That's what I need, changes at indexing time. Dynamic fields are not what I
need because the field name is the same, I just need to change if they
indexed/stored based on some logic.
It's so easily achieved with the Lucene API, I was sure there was a way to do
the same
Maria -
thanks for detailed explanation.
as per schema.xml; stored or indexed should be defined at schema design itself.
as per my understanding defining at runtime is not feasible.
BTW, you can have multiValued="true" attribute for dynamic fields too.
- Jeevanandam
On Apr 29, 2012, at 1:06
Maria,
thanks for detailed explanation.
as per schema.xml; stored or indexed should be defined at design-time.
Per my understanding defining at runtime is not feasible.
BTW, you can have multiValued="true" attribute for dynamic fields too.
- Jeevanandam
On 29-04-2012 2:06 am, Vazquez, Maria (
Thanks Jeevanandam.
That still doesn't have the same behavior as Lucene since multiple fields with
different names have to be created.
What I want is this exactly (multi-value field)
document.add(new Field("geoids", geoId, Field.Store.YES,
Field.Index.NOT_ANALYZED_NO_NORMS));
document.add(new F
Maria,
For your need please define unique pattern using dynamic field in schema.xml
Please have a look http://wiki.apache.org/solr/SchemaXml#Dynamic_fields
Hope that helps!
-Jeevanandam
Technology keeps you connected!
On Apr 28, 2012, at 10:33 PM, "Vazquez, Maria (STM)"
wrote:
> I can call
I can call a script for the logic part but what I want to figure out is how to
save the same field sometimes as stored and indexed, sometimes as stored not
indexed, etc. From a transformer or a script I didn't see anything where I can
modify that at indexing time.
Thanks a lot,
Maria
On Apr 27
As Bill mentioned, you can use Script.
Please have a look:
http://wiki.apache.org/solr/DataImportHandler#ScriptTransformer
- Jeevanandam
On Apr 28, 2012, at 7:07 AM, Bill Bell wrote:
> Yes you can. Just use a script that is called for each row.
>
> Bill Bell
> Sent from mobile
>
>
> On Apr
Yes you can. Just use a script that is called for each row.
Bill Bell
Sent from mobile
On Apr 27, 2012, at 6:38 PM, "Vazquez, Maria (STM)"
wrote:
> Hi,
> I'm migrating a project from Lucene 2.9 to Solr 3.4.
> There is a special case in the code that indexes the same field in two
> different
Hi,
I'm migrating a project from Lucene 2.9 to Solr 3.4.
There is a special case in the code that indexes the same field in two
different ways, which is completely legal in Lucene directly but I don't know
how to duplicate this same behavior in Solr:
if (isFirstGeo) {
document.add(new Fiel
13 matches
Mail list logo
