Our data comes from file system and from web and so adding the
auto-increment field at the datasource is not possible.
On Fri, Apr 6, 2012 at 6:50 PM, Shawn Heisey wrote:
> On 4/5/2012 1:53 AM, Manish Bafna wrote:
>
>> Hi,
>>> Is it possible to define a field as "Counter Column" which can be
>>>
On 4/5/2012 1:53 AM, Manish Bafna wrote:
Hi,
Is it possible to define a field as "Counter Column" which can be
auto-incremented.
Manish,
Where does your data come from? Can you add the autoincrement field to
the data source?
My data comes from MySQL, where the private key is an autoincreme
Yes, before indexing, we go and check whether that document is already
there in index or not.
Because along with the document, we also have meta-data information which
needs to be appended.
So, we have few multivalued metadata fields, which we update if the same
document is found again.
On Fri,
So you will need to do a search for each document before adding it to the
index, in case it is already there. That will be slow.
And where do you store the last-assigned number?
And there are plenty of other problems, like reloading after a corrupted index
(disk failure), or deleted documents w
Actually not.
If i am updating the existing document, i need to keep the old number
itself.
may be this way we can do it.
If we pass the number to the field, it will take that value, if we dont
pass it, it will do auto-increment.
Because if we update, i will have old number and i will pass it as a
Why?
When you reindex, is it OK if they all change?
If you reindex one document, is it OK if it gets a new sequential number?
wunder
On Apr 5, 2012, at 9:23 PM, Manish Bafna wrote:
> We already have a unique key (We use md5 value).
> We need another id (sequential numbers).
>
> On Fri, Apr 6,
We already have a unique key (We use md5 value).
We need another id (sequential numbers).
On Fri, Apr 6, 2012 at 9:47 AM, Chris Hostetter wrote:
>
> : We need to have a document id available for every document (Per core).
>
> : We can pass docid as one of the parameter for fq, and it will return
: We need to have a document id available for every document (Per core).
: We can pass docid as one of the parameter for fq, and it will return the
: docid in the search result.
So it sounds like you need a *unique* id, but nothing you described
requies that it be a counter.
Take a look at th
We need to have a document id available for every document (Per core).
There is DocID in Lucene Index but did not find any API to expose it using
Solr.
May be if we can alter Solr to optionally return the DocId (which is
unique),
We can pass docid as one of the parameter for fq, and it will retur
: > Is it possible to define a field as "Counter Column" which can be
: > auto-incremented.
a feature like this does not exist in Solr at the moment, but it would be
possible to implement this fairly easily in an UpdateProcessor -- however
it would only be functional in very limited situations
>
> Hi,
> Is it possible to define a field as "Counter Column" which can be
> auto-incremented.
>
> Thanks,
> Manish.
>
11 matches
Mail list logo
