You can replicate it with the example app by replacing the id definition in
schema.xml with
>
Removing the id fields in the one of the example doc.xml and posting it to solr.
Thanks
Viswa
On Sep 26, 2011, at 12:15 AM, Viswa S wrote:
> Hello,
>
> We use solr.UUIDField
Hello,
We use solr.UUIDField to generate unique ids, using the latest trunk (change
list 1163767) seems to throw an error "Document is missing mandatory uniqueKey
field: id". The schema is setup to generate a id field on updates
Thanks
Viswa
SEVERE: org.apache.solr.common.SolrException:
nd Date field issues
> >> From: erickerick...@gmail.com
> >> To: solr-user@lucene.apache.org
> >>
> >> H, this is puzzling. If you could come up with a couple of xml
> >> files and a schema
> >> that illustrate this, I'll see what I
If you could come up with a couple of xml
> files and a schema
> that illustrate this, I'll see what I can see...
>
> Thanks,
> Erick
>
> On Wed, May 4, 2011 at 7:05 PM, Viswa S wrote:
> >
> > Erik,
> >
> > I suspected the same, and setup a tes
x27;s just a guess. If this is really happening on a
> clean index it's a problem.
>
> I'm also going to guess that you're not really deleting the documents
> you think. Are you committing after the deletes?
>
> Best
> Erick
>
> On Wed, May 4, 2011 at
Hello,
The terms query for a date field seems to get populated with some weird dates,
many of these dates (1970,2009,2011-04-23) are not present in the indexed data.
Please see sample data below
I also notice that a delete and optimize does not remove the relevant terms for
date fields, the
usting
> to cater for these changes (e.g. deprecation of date range in favour
> of range). Have you tried this patch on 3x branch?
>
> Thanks,
> Peter
>
>
>
> On Fri, Mar 18, 2011 at 7:09 AM, Viswa S wrote:
> > Folks,
> >
> > We are trying to do some date face
Folks,
We are trying to do some date faceting on our distributed environment, applied
solr-1709 on the trunk. A date facet query throws the below exception, I have
attached the patched source for reference. Any help would be appreciated.
Other Info:
Java ver: 1_6_0_24
Trung change list: 1022
Hello,
I am trying to build source out of trunk (to apply a patch) and ran into an
issue were the build process hangs ( below output) during build lucene at
sanity-load-lib.
Just when build sanity-load-lib starts, I see an dialog box asking for applet
access permission "The applet is attemptin
our
> 'gut feel' is that it's not impacting the indexes very much size-wise or
> performance-wise.
>
> Bob Sandiford | Lead Software Engineer | SirsiDynix
> P: 800.288.8020 X6943 | bob.sandif...@sirsidynix.com
> www.sirsidynix.com
>
> > -Original Messa
://www.lucidimagination.com
>
> On Mon, Dec 13, 2010 at 10:00 PM, Viswa S wrote:
> >
> > Hello,
> >
> > We implemented an IP-Addr field type which internally stored the ips as
> > hex-ed string (e.g. "192.2.103.29" will be stored as "c002671d")
Hello,
We implemented an IP-Addr field type which internally stored the ips as hex-ed
string (e.g. "192.2.103.29" will be stored as "c002671d"). My "toExternal" and
"toInternal" methods for appropriate conversion seems to be working well for
query results, but however when faceting on this fie
or
> FieldName:[* TO *]? I'm betting you get all the docs back,
> but I've been very wrong before.
>
> Best
> Erick
>
> On Sat, Nov 20, 2010 at 5:02 PM, Viswa S wrote:
>
> >
> > Yes I do have a couple of documents with no values and one with an e
ame"?
>
> Best
> Erick
>
> On Sat, Nov 20, 2010 at 3:12 PM, Viswa S wrote:
>
> >
> > Folks,Am trying to query documents which have no values present, I have
> > used the following constructs and it doesn't seem to work on the solr dev
> >
Folks,Am trying to query documents which have no values present, I have used
the following constructs and it doesn't seem to work on the solr dev tip (as of
09/22) or the 1.4 builds.1. (*:* AND -FieldName[* TO *]) - returns no
documents, parsedquery was "+MatchAllDocsQuery(*:*) -FieldName:[* TO
Apologies for starting a new thread again, my mailing list subscription didn't
finalize till later than Yonik's response.
Using "Field1:Val1 AND (*:* NOT Field2:Val2)" works, thanks.
Does my original query "Field1:Value1 AND (NOT Field2:Val2)" fall into "need
the *:* trick if all of the clause
Dear Solr/Lucene gurus,
I have run into a weird issue trying use a negative condition in my query.
Parser:StandardQueryParserMy Query: Field1:Val1 NOT Field2:Val2Resolved as:
Field1:Val1 -Field2:Val2
The above query never returns any document, no matter how we use a paranthesis.
I did see some su
17 matches
Mail list logo