Hi,
Yes, maybe i can use a field multivalued , with
all my contents with a unique id.
My field "code" maybe can be a field multivalued ,
where each code is a diferente reference for the same content.
Can i directly update or remove one code inside
a multi-valued field ? Like this query:
- Need a
Can you explain a bit more? Because on the face
of it, "unique IDs but shared content" doesn't make
sense. The point of unique IDs is that they identify
documents uniquely.
A more usual setup is to have the content correspond
to the unique id. Is what you want really making your
"code" field multi
the tasks in one SolrQuery. I am creating
queries in Solrj.
-Original Message-
From: Raghunandan Rao [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 3:45 PM
To: solr-user@lucene.apache.org
Subject: RE: Unique id
Ok. I got your point. So I need not require ID field in the second view.
I w
PROTECTED]
Sent: Friday, November 21, 2008 3:45 PM
To: solr-user@lucene.apache.org
Subject: RE: Unique id
Ok. I got your point. So I need not require ID field in the second view.
I will hence remove required="true" in schema.xml. What I thought was
unique ID makes indexing easier or used t
PROTECTED]
Sent: Friday, November 21, 2008 3:36 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
Well, In that case, what do you want to search for? If I were you, I
would
make my index consist of tasks (and I assume that is what you are trying
to do).
So why don't you just use
Sorry for missing that column earlier. I think it should make sense now.
-Original Message-
From: Aleksander M. Stensby [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 3:18 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
And in case that wasn't clear, the reason for i
. Stensby [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 3:18 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
And in case that wasn't clear, the reason for it failing then would
obviously be because you define the id field with required="true", and
you
name (string), start (timestamp), end (timestamp))
2.
Team(person_id (int), deptId (int), isManager (int))
* is primary key
In schema.xml I have
id
-Original Message-
From: Aleksander M. Stensby [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 2:56 PM
To: solr-user@luc
(timestamp), end (timestamp))
2.
Team(person_id (int), deptId (int), isManager (int))
* is primary key
In schema.xml I have
id
-Original Message-
From: Aleksander M. Stensby [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 2:56 PM
To: solr-user@lucene.apache.org
Subject: Re:
, November 21, 2008 2:56 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
Hello again. I'm getting a bit confused by your questions, and I believe
it would be easier for us to help you if you could post the field
definitions from your schema.xml and the structure of your two database
ECTED]
Sent: Thursday, November 20, 2008 6:40 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
I'd suggest aggregating those three columns into a string that can
serve as the Solr uniqueKey field value.
Erik
On Nov 20, 2008, at 1:10 AM, Raghunandan Rao wrote:
Basically, I am work
definitions
in same schema. How does this work? Pls explain.
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 6:40 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
I'd suggest aggregating those three columns into a string that can
t: Re: Unique id
Technically, no, a uniqueKey field is NOT required. I've yet to run
into a situation where it made sense not to use one though.
As for indexing database tables - if one of your tables doesn't have a
primary key, does it have an aggregate unique "key" of some sort?
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 5:24 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
Technically, no, a uniqueKey field is NOT required. I've yet to run
into a situation where it made sense not to use one though.
As for indexing database tables - if o
Technically, no, a uniqueKey field is NOT required. I've yet to run
into a situation where it made sense not to use one though.
As for indexing database tables - if one of your tables doesn't have a
primary key, does it have an aggregate unique "key" of some sort? Do
you plan on updating
uot;some
query2");
-Original Message-
From: Aleksander M. Stensby [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 4:22 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
Ok, but how do you map your table structure to the index? As far as I
can
understand, the two t
doing
update.
How does this work? Please explain.
Thanks.
-Original Message-
From: Aleksander M. Stensby [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 3:49 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
Yes it is. You need a unique id because the add method works
update.
How does this work? Please explain.
Thanks.
-Original Message-
From: Aleksander M. Stensby [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 3:49 PM
To: solr-user@lucene.apache.org
Subject: Re: Unique id
Yes it is. You need a unique id because the add method works as
Yes it is. You need a unique id because the add method works as and "add
or update" method. When adding a document whose ID is already found in the
index, the old document will be deleted and the new will be added. Are you
indexing two tables into the same index? Or does one entry in the inde
Evgeniy Strokin wrote:
If I make one of my field as a unique ID, id doesn't increase/decrease
performance of searching by this field. Right?
For example if I have two fields, I know for sure both of them are unique, both
the same type, and make one of them as a Solr Unique ID. The general
perf
On 4/10/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
> : Is there any way to explicitly add a record using Solr, such that the
> : add will fail if a record already exists with the same value in the
> : unique ID field (as specified by the schema's uniqueKey field)?
>
> I was going to say over
: Is there any way to explicitly add a record using Solr, such that the
: add will fail if a record already exists with the same value in the
: unique ID field (as specified by the schema's uniqueKey field)?
I was going to say should do what you want,
http://wiki.apache.org/solr/UpdateXmlMessa
22 matches
Mail list logo
