On Mon, Jul 28, 2014 at 1:31 PM, Elran Dvir wrote:
> But when no value is sent with severity, and the default of 0 is used, the
> fix doesn't seem to work.
I guess the default in this case is figured out at the query time
because there is no empty value as such. So that would be too late for
cop
Hi all,
I have an enumField called severity.
these are its relevant definitions in schema.xml:
And in enumsConfig.xml:
Not Available
Low
Medium
High
Critical
The default field for free text search is text.
An enum field can be sent with its integer
I'm benchmarking this right now so I'll share some numbers soon.
On Mon, Jul 28, 2014 at 12:45 AM, Erick Erickson
wrote:
> bq: Whoa! That's awesome!
>
> And scary.
>
> Ian: Thanks a _lot_ for trying this out and reporting back.
>
> Also, let me say that this was a nice writeup, I wish more
Hi Shawn
No affense to your work,I am still confusing about the cache warm
processing about your explanation.So I check the warm method of
FastLRUCache as [1].
As far as I see,there is no values refresh during the the warm
processing. the *regenerator.regenerateItem* just put the old value to
Hi Erick
We do the DIH job from the DB and committed frequently.It takes a long time
to autowarm the filterCaches after commit or soft commit happened when
setting the autowarmcount=1024,which I do think is small enough.
So It comes up an idea that whether it could directly pass the reference
o
On Sun, Jul 27, 2014 at 12:28 PM, Gora Mohanty wrote:
> On 27 July 2014 12:13, Aniket Bhoi wrote:
>
> > On Fri, Jul 25, 2014 at 8:32 PM, Aniket Bhoi
> > wrote:
> >
> > > I have Apache Solr,hosted on my apache Tomcat Server with SQLServer
> > > Backend.
> >
> > [...]
>
> > > After I run a full i
On 7/27/2014 7:23 PM, Nathan Neulinger wrote:
> Unfortunately, doesn't look like this clears the symptom.
>
> The ping is responding almost instantly every time. I've tried setting a
> 15 second timeout on the check, with no change in occurences of the error.
>
> Looking at a packet capture on th
Either way, looks like this is not a SOLR issue, but rather haproxy.
Thanks.
-- Nathan
On 07/27/2014 08:23 PM, Nathan Neulinger wrote:
Unfortunately, doesn't look like this clears the symptom.
The ping is responding almost instantly every time. I've tried setting a 15
second timeout on the c
Unfortunately, doesn't look like this clears the symptom.
The ping is responding almost instantly every time. I've tried setting a 15 second timeout on the check, with no change
in occurences of the error.
Looking at a packet capture on the server side, there is a clear distinction between wor
Cool. That's likely exactly it, since I don't have one set, it's using the check interval, and occasionally must just be
too short.
Thank you!
-- Nathan
I assume that this is the httpchk config to make sure that the server is
operational. If so, you need to increase the "timeout check" valu
On 7/27/2014 8:37 AM, Shalin Shekhar Mangar wrote:
> I found SOLR-4839 so we'll use that issue.
>
> https://issues.apache.org/jira/browse/SOLR-4839
I hope you have better luck than I did. It wasn't a simple matter of
upgrading the jars and locating simple API changes, a job that I've
tackled a f
On 7/26/2014 5:15 PM, Nathan Neulinger wrote:
> Recently deployed haproxy in front of my solr instances, and seeing a
> large number of exceptions in the logs now... Example below. I can pound
> the server with requests against /solr/admin/ping via curl, with no
> obvious issue, but the haproxy che
Have you tried the getFieldStatsInfo method in the QueryResponse object?
Best,
Erick
On Sat, Jul 26, 2014 at 3:36 PM, Edith Au wrote:
> I have a solr query like this
>
> q=categories:cat1 OR
> categories:cat2&stats=true&stats.field=count&stats.facet=block_num
>
> Basically, I want to get the s
bq: Whoa! That's awesome!
And scary.
Ian: Thanks a _lot_ for trying this out and reporting back.
Also, let me say that this was a nice writeup, I wish more people would post
as thorough a problem statement!
Best,
Erick
On Sat, Jul 26, 2014 at 5:08 AM, Shalin Shekhar Mangar <
shalinman...@
H, well _I_ don't know what to say then
This is puzzling. How much of a latency difference are you seeing?
It'd be interesting to see what happens if you experiment with
only going to a single shard (add &distrib=false to the query). Each
cache is local to the shard, so it's vaguely possi
Why do you think you _need_ to autowarm the entire cache? It
is, after all, an LRU cache, the theory being that the most recent
queries are most likely to be reused.
Personally I'd run some tests on using small autowarm counts
before getting at all mixed up in some complex scheme that
may not be u
"Does not play nice" really means it was designed to run in a
non-distributed mode. There has
been no work done to verify that it does work in cloud mode, I fully expect
some "interesting"
problems in that mode. If/when we get to it that is.
About replication: I haven't heard of any problems, but
Hi,
Can't you use elevateIds parameter?
https://wiki.apache.org/solr/QueryElevationComponent#elevateIds.2FexcludeIds
On Thursday, July 24, 2014 2:30 PM, rahulmodi wrote:
Thanks a lot Erick,
i have looked at Query Elevation Component, it works but the problem is if i
need to add new tag or up
No, although there's been some joy with using shingles. Autosuggest
works off of the _indexed tokens_. So the problem is really reducing
the tokenization to something that is multi-word.
Best,
Erick
On Thu, Jul 24, 2014 at 5:11 AM, benjelloun wrote:
> Hello,
>
> Did solr.SuggestComponent work
Yep, Query Elevation is a pretty blunt instrument. You should
be able to get the configuration file to re-load by issuing a reload
command rather than re-starting.
But your problem of having a bunch of different queries
return the same top doc is, indeed, the problem. You need
a complete list of q
May be you miss that your field "dom_title" should be
index="true" termVectors="true" termPositions="true" termOffsets="true"
I found SOLR-4839 so we'll use that issue.
https://issues.apache.org/jira/browse/SOLR-4839
On Sun, Jul 27, 2014 at 8:06 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> Yes, we are on Java7 so we can move now. I'll open an issue.
>
>
> On Sun, Jul 27, 2014 at 5:39 AM, Bill Bell wro
Yes, we are on Java7 so we can move now. I'll open an issue.
On Sun, Jul 27, 2014 at 5:39 AM, Bill Bell wrote:
> Since we are now on latest Java JDK can we move to Jetty 9?
>
> Thoughts ?
>
> Bill Bell
> Sent from mobile
>
>
--
Regards,
Shalin Shekhar Mangar.
I was reviewing the httpclient code in HttpSolrServer and noticed that it sets
a "Content-Charset" header. As far as I know this is not a real header and is
not necessary. Anyone know a reason for this to be there? I'm guessing this was
just a mistake when converting from httpclient3 to httpclie
I always get the "Loading" message on the Solr Admin Console if I use IE.
However - the page loads perfectly fine when I use Google Chrome or Mozilla
Firefox.
Could you check if your problem resolves itself if you use a different
browser ???
--
View this message in context:
http://lucene.47206
Right, and that's exactly what DataStax Enterprise provides (at great
engineering effort!) - synchronization of database updates and search
indexing. Sure, you can do it as well, but that's a significant engineering
challenge with both sides of the equation, and not a simple "plug and play"
con
On 27 July 2014 12:13, Aniket Bhoi wrote:
> On Fri, Jul 25, 2014 at 8:32 PM, Aniket Bhoi
> wrote:
>
> > I have Apache Solr,hosted on my apache Tomcat Server with SQLServer
> > Backend.
>
> [...]
> > After I run a full import,Indexing proceeds sucessfully,but seems to
> > freeze everytime after
27 matches
Mail list logo
