Thanks Aurélien
On Aug 19, 2014 3:00 PM, "jmlucjav" wrote:
> In the sample schema.xml I can see this:
>
>
> multiValued="true"/>
>
>
> I am wondering, how does having this split in two fields text/content save
> space?
>
"indexed" means you can search it, "stored" means you can return the
value to the user or highlight it.
Both consum disk space.
A copyfield is not a kind of special field : it is a directive that
copies one field values to another field. They are many use cases for
using copy fields.
In the exa
no it does not.
Here the intent, I think, is not to duplicate stored info, as other
metadata fields like author, keywords etc already are stored, if 'text' was
stored (text is where all fields: content, author etc are copyed), then it
would contain some duplicate info.
On Tue, Aug 19, 2014 at 1:
I have a question, does storing the data in copyfields save space?
With Regards
Aman Tandon
On Tue, Aug 19, 2014 at 3:02 PM, jmlucjav wrote:
> ok, I had not noticed text contains also the other metadata like keywords,
> description etc, nevermind!
>
>
> On Tue, Aug 19, 2014 at 11:28 AM, jmlucj
ok, I had not noticed text contains also the other metadata like keywords,
description etc, nevermind!
On Tue, Aug 19, 2014 at 11:28 AM, jmlucjav wrote:
> In the sample schema.xml I can see this:
>
>
> stored="true" multiValued="true"/>
>
>
> I am wondering, how does having this split
In the sample schema.xml I can see this:
I am wondering, how does having this split in two fields text/content save
space?
> Not particularly. Just trying to do my part to answer some questions on
> the list.
>
> -Original Message-
> From: Steve Cerny [mailto:sjce...@gmail.com]
> Sent: Tuesday, August 16, 2011 11:49 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Product data schema question
&g
Not particularly. Just trying to do my part to answer some questions on the
list.
-Original Message-
From: Steve Cerny [mailto:sjce...@gmail.com]
Sent: Tuesday, August 16, 2011 11:49 AM
To: solr-user@lucene.apache.org
Subject: Re: Product data schema question
Thanks Jay, if we come to
011 11:37 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Product data schema question
>
> Jay, this is great information.
>
> I don't know enough about Solr whether this is possible...Can we setup two
> indexes in the same core, one for product_catalog and the other for
s an index.
-Original Message-
From: Steve Cerny [mailto:sjce...@gmail.com]
Sent: Tuesday, August 16, 2011 11:37 AM
To: solr-user@lucene.apache.org
Subject: Re: Product data schema question
Jay, this is great information.
I don't know enough about Solr whether this is possible...Can we setup
gt; the faceting on variant inventory.
>
> -Original Message-
> From: Steve Cerny [mailto:sjce...@gmail.com]
> Sent: Monday, August 15, 2011 6:29 PM
> To: solr-user@lucene.apache.org
> Subject: Product data schema question
>
> I'm working on an online eCommer
f course, that won't help with the faceting on variant
inventory.
-Original Message-
From: Steve Cerny [mailto:sjce...@gmail.com]
Sent: Monday, August 15, 2011 6:29 PM
To: solr-user@lucene.apache.org
Subject: Product data schema question
I'm working on an online eCommerce
I'm working on an online eCommerce project and am having difficulties
building the core / index schema. Here is the way we organize our product
information in a normalized database.
A product model has many SKUs (called colorways)
A SKU has many sizes (called variants)
A SKU size has associated i
Highlighting is a complex topic. A field has to be stored to be
highlight. It does not have to be indexed. But, if it is not,
highlighting analyzes it just like if it was indexed in order to
highlight it.
http://www.lucidimagination.com/search/document/CDRG_ch07_7.9?q=highlighting
http://www.luci
Thanks everyone, It works! I have successfully indexed them. Thanks again!
I have couple of more questions regarding with solr, if you don't mind.
1-) As I said before, the text files are quite large, between
100kb-10mb, but I need to store them as well for highlighting,
including with their titl
Man you people are fast!
There is a bug in Solr/Lucene. It keeps memory around from previous
fields, so giant text files might run out of memory when they should
not. This bug is fixed in the trunk.
On 4/17/10, Lance Norskog wrote:
> The DataImportHandler can let you fetch the file name from the
The DataImportHandler can let you fetch the file name from the
database record, and then load the file as a field and process the
text with Tika.
It will not be easy :) but it is possible.
http://wiki.apache.org/solr/DataImportHandler
On 4/17/10, Serdar Sahin wrote:
> Hi,
>
> I am rather new to
> I am rather new to Solr and have a question.
>
> We have around 200.000 txt files which are placed into the
> file cloud.
> The file path is something similar to this:
>
> file/97/8f/840/fa4-1.txt
> file/a6/9d/ab0/ca2-2.txt etc.
>
> and we also store the metadata (like title, description,
> ta
Hi Serdar,
take a look at Solr's DataImportHandler:
http://wiki.apache.org/solr/DataImportHandler
Best,
Sascha
Serdar Sahin wrote:
Hi,
I am rather new to Solr and have a question.
We have around 200.000 txt files which are placed into the file cloud.
The file path is something similar to th
Hi,
I am rather new to Solr and have a question.
We have around 200.000 txt files which are placed into the file cloud.
The file path is something similar to this:
file/97/8f/840/fa4-1.txt
file/a6/9d/ab0/ca2-2.txt etc.
and we also store the metadata (like title, description, tags etc)
about the
Yeah, probably the SignatureUpdateProcessorFactory can do the trick, but
you still need to write a custom Signature.
(we should really offer a simple "ConcatSignature" implementation for
generating predictable combination keys)
+1
Cheers,
Uri
Chris Hostetter wrote:
: TemplateTranformer. Other
: TemplateTranformer. Otherwise, if you really must do it in Solr you can write
: your own custom UpdateProcessor and plug it in:
Can't the SignatureUpdateProcessorFactory handle this using something like
Lookup3Signature?
(we should really offer a simple "ConcatSignature" implementation for
g
Using copyField will add three different values to the unique id
field; it will not concatenate them into one value. It has to be a
single-valued field. The three values have to be concatenated in DIH
or in the feeding application.
On Sun, Jan 17, 2010 at 6:41 PM, William Bell wrote:
> You could
You could use a copyField.
On 1/17/10 1:47 PM, "Koji Sekiguchi" wrote:
> Pradeep Pujari wrote:
>> how can I specify uniqueKey value in schema.xml as a concatenation of 3
>> columns. Like prod_id+attr_name+att_value?
>>
>> Thanks,
>> Pradeep
>>
>>
> Solr doesn't support it. You should conca
If you're using DataImportHandler than this can easily be done with a
TemplateTranformer. Otherwise, if you really must do it in Solr you can
write your own custom UpdateProcessor and plug it in:
DIH TemplateTransformer:
http://wiki.apache.org/solr/DataImportHandler#TemplateTransformer
Update
Pradeep Pujari wrote:
how can I specify uniqueKey value in schema.xml as a concatenation of 3
columns. Like prod_id+attr_name+att_value?
Thanks,
Pradeep
Solr doesn't support it. You should concatenate them at client.
Koji
--
http://www.rondhuit.com/en/
how can I specify uniqueKey value in schema.xml as a concatenation of 3
columns. Like prod_id+attr_name+att_value?
Thanks,
Pradeep
: Unfortunately, unless I've missed something obvious, the "tokenized"
: property is not available to classes that extend FieldType: the setArgs()
: method of FieldType strips "tokenized" and other standard properties away
: before calling the init() method. Yes, of course one could override
: set
Chris Hostetter <[EMAIL PROTECTED]> wrote on 05/31/2007 02:28:58
PM:
> I'm having a little trouble following this discussion, first off as to
> your immediate issue...
>
> : Thanks, but I think I'm going to have to work out a different
solution. I
> : have written my own analyzer that does ever
On 5/31/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
...maybe there is some terminology confusion here
I think the issue is the additional restrictions:
"consolidate all field properties to the field element. The reason for
this is that the schema is read by another class to give access to
f
I'm having a little trouble following this discussion, first off as to
your immediate issue...
: Thanks, but I think I'm going to have to work out a different solution. I
: have written my own analyzer that does everything I need: it's not a
: different analyzer I need but a way to specify that
On 31-May-07, at 8:47 AM, [EMAIL PROTECTED] wrote:
Thanks, but I think I'm going to have to work out a different
solution. I
have written my own analyzer that does everything I need: it's not a
different analyzer I need but a way to specify that certain fields
should
be tokenized and others
Thanks, but I think I'm going to have to work out a different solution. I
have written my own analyzer that does everything I need: it's not a
different analyzer I need but a way to specify that certain fields should
be tokenized and others not -- while still leaving all other options open.
As
On 5/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
You say the "tokenized" attribute is not settable from the schema, but the
output from IndexSchema.readConfig shows that the properties are indeed
read, and the resulting SchemaField object retains these properties: are
they then ignored?
Thanks for the prompt response. Comments below ...
[EMAIL PROTECTED] wrote on 05/31/2007 10:55:57 AM:
> On 5/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > I am trying to override the tokenized attribute of a single FieldType
from
> > the field attribute in schema.xml, but it doesn't se
On 5/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I am trying to override the tokenized attribute of a single FieldType from
the field attribute in schema.xml, but it doesn't seem to work
The "tokenized" attribute is not settable from the schema, and there
is no reason I can think of why
I am trying to override the tokenized attribute of a single FieldType from
the field attribute in schema.xml, but it doesn't seem to work and I can't
figure out why. For example, if I define various fields to be of type
solr.TextField, and use tokenized="false" for some and tokenized="true"
for
37 matches
Mail list logo
