my goal is to run a query and limit it with the timestamp of the last
document i found. will TrieDateField give me this precision? is there any
other way to achieve that?
i also see slow queries when using a filter on a field that is a simple
string(StrField), that has only 3 types of values, don
hi all,
now solr is working good.i am working in ubuntu and i was indexing
the documents which dont hav permissions . so the problem was that. i thank
all of u for ur reply to my queries.
thanking you,
satya
> I have a query that seems to be running much slower when i
> try to filter it.
> the field is of type pdate (solr.DateField) and the filter
> is for example
> timestamp:[2010-01-01T00:00:00Z TO NOW] (to look only for
> documents since
> Jan 1st.
> if i don't use the filter, the query returns pret
sorry for not mentioning it, we use solr 1.4.1
thanks again for any idea
--
View this message in context:
http://lucene.472066.n3.nabble.com/filter-query-on-timestamp-slowing-query-tp977280p977299.html
Sent from the Solr - User mailing list archive at Nabble.com.
I have a query that seems to be running much slower when i try to filter it.
the field is of type pdate (solr.DateField) and the filter is for example
timestamp:[2010-01-01T00:00:00Z TO NOW] (to look only for documents since
Jan 1st.
if i don't use the filter, the query returns pretty fast, but ad
Also, if you're using multicore, you can set the property in the main
solr.xml. This at least puts everything in one place on that server.
On Sun, Jul 18, 2010 at 12:36 PM, Chris Hostetter
wrote:
>
> : 'Alternately: you can specifiy the solr.data.dir system property at run
> time'
> :
> : shou
You can make two spellcheckers and consult both of them.
A spelling database made from an existing text index tends to have a
lot of confusing junk.
On Sun, Jul 18, 2010 at 4:43 AM, wrote:
> Can i make a dictionnary of only the words that are having problems? There
> are not that many terms tha
: SimplePostTool: FATAL: Solr returned an error:
: Illegal_character_CTRLCHAR_code_27__at_rowcol_unknownsource_37022847
:
: I've tried to track where this problem is located without luck.
check your solr logs, it will contain the "unmunged" version of the error
message (the the version of jetty
: 'Alternately: you can specifiy the solr.data.dir system property at run
time'
:
: should yield the exact result I'm looking for - runtime configuration of
multiple instances.
:
: Thanks for the full reply.
To be clear: solr.data.dir isn't any sort of special setting -- that
systemproper
Hoss,
The comment at the end:
'Alternately: you can specifiy the solr.data.dir system property at run time'
should yield the exact result I'm looking for - runtime configuration of
multiple instances.
Thanks for the full reply.
Regards,
Tracy
On Jul 18, 2010, at 3:23 PM, Chris Hostetter
: I think the history of that might involve back compat issues.
Correct.
Tracy: the *default* location for dataDir, if you have nothing specified
in your solrconfig.xml is to be relative your Solr Home ... but if you
specify a path, that path is resolved relative the CWD.
One of the use cases
For xml 1.1 documents, you can view if any of your documents have
these restricted characters defined here:
http://www.w3.org/TR/2006/REC-xml11-20060816/#NT-RestrictedChar
If they are, you'll have to remove them.
didier
On Sun, Jul 18, 2010 at 11:16 AM, robert mena wrote:
> Hi,
>
> I am doing s
Hi,
I am doing some tests with solr 1.4.1.
I've created a XML file with the documents I'd like to index. With a few
items (1000) everything went fine.
When I went to a more representative import (around 6) I got error
java -jar example/exampledocs/post.jar doc.xml
SimplePostTool: version
Have you read:
http://wiki.apache.org/lucene-java/ImproveIndexingSpeed
http://www.lucidimagination.com/Community/Hear-from-the-Experts/Articles/Scaling-Lucene-and-Solr
To be short there are only guidelines (see links) no definitive answers.
If you followed the guidelines for improviing indexing sp
I think the history of that might involve back compat issues.
- Mark
On 7/18/10 7:23 AM, Tracy Flynn wrote:
> Koji,
>
> Thanks for that information. That at least offers a work-around for the
> problem.
>
> When I look at the general description of 'solr.solr.home' and the specific
> comments
No one has done performance analysis? Or has a link to anywhere where it's
been done?
basically fastest way to get documents into Solr. So many options available,
what's the fastest:
1) file import (xml, csv) vs DIH vs POSTing
2) number of concurrent clients 1 vs 10 vs 100 ...is there a di
Can i make a dictionnary of only the words that are having problems? There
are not that many terms that present this behavior, but it is important for
me to get rid of this bug. So can i use the dictionnary AND the list built
by the spellchecker?
-Original Message-
From: Lance Norskog
Koji,
Thanks for that information. That at least offers a work-around for the problem.
When I look at the general description of 'solr.solr.home' and the specific
comments for 'dataDir' in 'solrconfig.xml', the clear implication is that, if
nothing is changed, the dataDir value should be expect
(10/07/18 10:03), Tracy Flynn wrote:
That's a little telling
INFO: Opening new SolrCore at /Users/johndoe/example1/solr/,
dataDir=./solr/data/
Since I'm running with ~/example2 as the current working directory, then that
would explain it. Schema etc. is found in ~/example1/solr/conf, but the
Hi Jonathan,
Once again many thanks for your guidance. I made it work this time :-)
Thanks,
Balaji.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Get-only-partial-match-results-tp963212p976106.html
Sent from the Solr - User mailing list archive at Nabble.com.
20 matches
Mail list logo