On 6/16/2016 1:20 AM, Bharath Kumar wrote:
> I was trying to generate a solr war out of the solr 6 source, but even
> after i create the war, i was not able to get it deployed correctly on
> jboss. Wanted to know if anyone was able to successfully generate solr
> war and deploy it on tomcat or jbos
Thanks Erick - that's what we have settled on doing until we are using
SolrCloud, which will be later this year with any luck. We want to get up
onto Solr 5.5.1 first (ASAP) and we tried disabling tlogs today and that
seems to fit the bill.
Fr
Hi Guys,
Thank you all - I got synonyms, highlighting, stemming all working the way I
wanted to.
I am sure I will have more questions later on =)
Thanks!
Sas
If you are NOT using SolrCloud and don't
care about Real Time Get, you can just disable the
tlogs entirely. They're not doing you all that much
good in that case...
The tlogs are irrelevant when it comes to master/slave
replication.
FWIW,
Erick
On Fri, Jun 17, 2016 at 9:14 AM, Chris Morley wrot
> OK - Slapping forehead now... D'oh!
>
> 1.2
> Float, not int!
>
LOL, we've all been there. I'm surprised I didn't notice that myself.
MJ
OK - Slapping forehead now... D'oh!
1.2 wrote:
> Hi all -
>
> I've successfully run the hon-lucene-synonyms plugin from the Admin
> console by adding the following to the Raw Query Parameters field...
>
>
> &qf=text&defType=synonym_edismax&synonyms=true&synonyms.originalBoost=1.2&synonyms.synonym
On Fri, Jun 17, 2016 at 2:15 PM, John Bickerstaff
wrote:
> If I do NOT add the last line and only have the line that sets
> synonyms=true, it appears to work fine.
>
> I see the dot notation all over the sample entries in solrconfig.xml... Am
> I missing something here?
>
> Essentially, how do I
Hi all -
I've successfully run the hon-lucene-synonyms plugin from the Admin console
by adding the following to the Raw Query Parameters field...
&qf=text&defType=synonym_edismax&synonyms=true&synonyms.originalBoost=1.2&synonyms.synonymBoost=1.1
I got those from the Read Me on the github account
I try to adjust the new generation size so that it can handle all the
allocations needed for HTTP requests. Those short-lived objects should never
come from tenured space.
Even without facets, I run a pretty big new generation, 2 GB in an 8 GB heap.
The tenured space will always grow in Solr, b
Hi,
May be URL encoding issue?
By the way, I would use back slash to escape special characters.
Ahmet
On Friday, June 17, 2016 10:08 AM, Zheng Lin Edwin Yeo
wrote:
Hi,
I encountered this error when I tried to search with special characters,
like "&" and "#".
{
"responseHeader":{
"st
For what it’s worth, I looked into reducing the allocation footprint of
CollapsingQParserPlugin a bit, but without success. See
https://issues.apache.org/jira/browse/SOLR-9125
As it happened, I was collapsing on a field with such high cardinality that the
chances of a query even doing much coll
I was just looking at SolrCellBuilder, and it looks like there's an assumption
that documents will not have attachments/embedded objects. Unless I
misunderstand the code, users will not be able to search documents inside zips,
or attachments in msg/ doc/pdf/etc (cf. SOLR-7189).
Are embedded do
Really we need the infoStream output, to see what IW is doing, to take so
long merging.
Likely only one merge thread is running (CMS tries to detect if your IO
system "spins" and if so, uses 1 merge thread) ... maybe try configuring
this to something higher since your RAID array can probably handl
Hi,
I would like to check the response for the *authors *data that comes in my
multiValued *authors* field and do some activity related to it before the
output is send back.
I know to access the facets and investigate it.
Could some one pls advise (the apis/ methods etc) on how I can get started
After some more searching, I found a thread online where Erick Erickson is
telling someone about how there are old tlogs left around in case there is
a need for a peer to sync even if SolrCloud is not enabled. That makes
sense, but we'll probably want to enable autoCommit and then trigger
repl
17 June 2016, Apache Solr 6.1.0 available
Solr is the popular, blazing fast, open source NoSQL search platform from
the Apache Lucene project. Its major features include powerful full-text
search, hit highlighting, faceted search and analytics, rich document
parsing, geospatial search, extensive R
17.6.2016, 11.05, Bernd Fehling kirjoitti:
Am 17.06.2016 um 09:06 schrieb Ere Maijala:
16.6.2016, 1.41, Shawn Heisey kirjoitti:
If you want to continue avoiding G1, you should definitely be using
CMS. My recommendation right now would be to try the G1 settings on my
wiki page under the headi
Am 17.06.2016 um 09:06 schrieb Ere Maijala:
> 16.6.2016, 1.41, Shawn Heisey kirjoitti:
>> If you want to continue avoiding G1, you should definitely be using
>> CMS. My recommendation right now would be to try the G1 settings on my
>> wiki page under the heading "Current experiments" or the CMS
Hi,
I encountered this error when I tried to search with special characters,
like "&" and "#".
{
"responseHeader":{
"status":400,
"QTime":0},
"error":{
"msg":"org.apache.solr.search.SyntaxError: Cannot parse
'\"Research ': Lexical error at line 1, column 11. Encountered:
after :
16.6.2016, 1.41, Shawn Heisey kirjoitti:
If you want to continue avoiding G1, you should definitely be using
CMS. My recommendation right now would be to try the G1 settings on my
wiki page under the heading "Current experiments" or the CMS settings
just below that.
For what it's worth, we're
20 matches
Mail list logo