Hi,
Please find below the console logs for the above issue we have been facing:
org.apache.solr.common.SolrException: Error opening new searcher
at org.apache.solr.core.SolrCore.(SolrCore.java:824)
at org.apache.solr.core.SolrCore.(SolrCore.java:665)
at
Hi,
We have been facing the problem of corrupted solr index, after restoring
our data. When we restore the data, the status shows 'success' after some
time. But later, when we make some config changes and then try to stop the
instance and restart it with the new configurations - the index is
Hi Janit,
Please ask these questions the solr-user mailing list. There is no point in
double posting to the dev list as well.
Looking at the stacktrace it looks like the index files are corrupted. On
the backed up index can you run the CheckIndex
command to see what it says. The command would
>From what I have experienced, the performance using edismax will be slower.
It may not be that significant if your index size is small, but it will get
more significant as your index size grows.
By the way, which version of Solr are you using?
Regards,
Edwin
On 29 February 2016 at 21:33,
Shawn, not sure if it's the same case as yours, but I've hit NPEs upgrading
to 5.5 too. In my case though, SolrJ talks to a proxy servlets before the
request gets routed to Solr, and that servlet didn't handle binary content
stream well.
I had to add another resource method to the servlet which
I am a new to solr and servers in general. I am using Solr 5.5.0 on a
Raspberry Pi 2 running Ubuntu trusty. I can start the solr server, and
visit the admin page, but when I try to run something like 'bin/solr create
-c testcore' I recieve:
*INFO - 2016-03-01 02:26:41.595;
On 2/29/2016 7:01 PM, Shawn Heisey wrote:
> On 2/29/2016 6:42 PM, Shawn Heisey wrote:
>> I'm getting this stacktrace after upgrading SolrJ to 5.5.0 in my build
>> client:
>>
>> http://apaste.info/Vpg
>>
>> This is happening with 4.x, 5.3.2-SNAPSHOT, and 5.5.0-SNAPSHOT servers.
> I got a little bit
Hi Roshan,
This is first time I am hearing about parboiled, but please see wiki page for
commercial support
https://wiki.apache.org/solr/Support
Ahmet
On Tuesday, March 1, 2016 3:15 AM, SIDDHAST® Roshan wrote:
Dear Solr and lucene group memebers
We are on a parboiled
On 2/29/2016 6:42 PM, Shawn Heisey wrote:
> I'm getting this stacktrace after upgrading SolrJ to 5.5.0 in my build
> client:
>
> http://apaste.info/Vpg
>
> This is happening with 4.x, 5.3.2-SNAPSHOT, and 5.5.0-SNAPSHOT servers.
I got a little bit closer look at the server log. Initially it
I'm getting this stacktrace after upgrading SolrJ to 5.5.0 in my build
client:
http://apaste.info/Vpg
This is happening with 4.x, 5.3.2-SNAPSHOT, and 5.5.0-SNAPSHOT servers.
If I configure ivy to pull solrj 5.4.1 instead of the latest version,
everything works without changing the code.
I
I mean to create several different fields that are indexed differently
(and not stored). So one could be indexed with minimal processing and
another with more aggressive one but with less weight.
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
Dear Solr and lucene group memebers
We are on a parboiled parser for solr. We are facing a small issue
regarding the rule construction in parboiled. We would like some one in
lucene apache qroup to guide us on this issue with your expert knowledge.
Please let us know if members in group with
On 2/29/2016 4:09 PM, Marcin T wrote:
> Since Solr 5.x there is no web archive (war) in standard distribution.
> So I'm building a web archive (war) and I'm deploying it in my Tomcat
> 8 container. It works to Solr 5.3. Since Solr 5.4 it doesn't works
> How can I solve this problem?
Don't deploy
Hi Alex
Can you advice how can I make use of copyField to handle this issue?
NLP lematisation will be the last resort and subject to budget and
business usersdecision.
Derek
On 3/1/2016 8:13 AM, Alexandre Rafalovitch wrote:
On 29 February 2016 at 20:40, Derek Poh
Hi Emir
For my use case, it is to do a exact match (enclosed searchkeyword in
double quotes) on a search field. Searchon "power banks" should return
matches for "power bank" and "power banks", singular and plural forms.
I will need to do furthertesting with porterstemfilter to ensure it meet
Thanks Timothy for your prompt help.
I tried first option. I am able to extract .eml ( MIME format) files from
PST file using libpst library.
I am not able extract .msg ( outlook emails) files using libpst library. I
am able to feed .eml files into SOLR.
I can see some of tags are missing in
On 29 February 2016 at 20:40, Derek Poh wrote:
> Is there other filter factory that can reduce pluralto singular correctly?
English is not an easy language and most of the heuristic filters have
issues. You could try copyField and multiple approaches.
Or, if this is a
On 29 February 2016 at 09:40, wrote:
> I have no problem with automatic. It is "automagicall" stuff that I find a
> bit hard to like. Ie things that are automatic, but doesn't explain how and
> why they are automatic. But Disney Land and Disney World are
Hi,
Since Solr 5.x there is no web archive (war) in standard distribution.
So I'm building a web archive (war) and I'm deploying it in my Tomcat
8 container. It works to Solr 5.3. Since Solr 5.4 it doesn't works
(admin's page doesn't works). A problem is with
Hi, I use solr 4.2
In schema.xml I created the following filed type:
**
"bn_synonyms.txt" contains:
*testword=>test word*
Interesting... if I google for "edismax solr" (I usually specify a product
name when searching for doc by feature name to avoid irrelevant hits) the
old wiki comes up as #1 and new doc as #2, but if I search for "edismax"
alone (which I normally wouldn't do out of a desire to limit matches to the
It is indeed a problem that the old edismax wiki is result #1 from Google.
I find that annoying as well since I also use Google search as my first
step in accessing doc on everything.
-- Jack Krupansky
On Mon, Feb 29, 2016 at 10:03 AM,
wrote:
> Thanks
Thanks Shawn,
I had more or less assumed that the cwiki site was focused on the latest Solr
version, but never really noticed that the "reference guide" was available in
version-specific releases. I guess that is partly because I prefer googling
about a specific topic, instead of reading some
Well, I have to say that I strongly disagree with you. No regular user should
have to resort to the source code to understand that edismax is preconfigured.
Because that is what this is all about, in essence. The current documentation
doesn't mention this, and the only documentation about
On 2/29/2016 7:00 AM, jimi.hulleg...@svensktnaringsliv.se wrote:
> So, should I assume that the "Confluence wiki" is the correct place for all
> documentation, even for solr 4.6?
If you want documentation specifically for 4.6, there are
version-specific releases of the guide:
thanks Shawn, that seems to be the error exactly.
On 02/29/2016 09:22 AM, Shawn Heisey wrote:
On 2/28/2016 3:31 PM, David Santamauro wrote:
I'm porting a 4.8 schema to 5.3 and I came across this new error when
I tried to group.field=f1:
unexpected docvalues type SORTED_SET for field 'f1'
On 2/28/2016 3:31 PM, David Santamauro wrote:
>
> I'm porting a 4.8 schema to 5.3 and I came across this new error when
> I tried to group.field=f1:
>
> unexpected docvalues type SORTED_SET for field 'f1' (expected=SORTED).
> Use UninvertingReader or index with docvalues.
>
> f1 is defined as
>
>
Hi,
We are facing an issue during a migration from Solr4 to Solr5.
Given
- migration from solr 4.10.4 to 5.4.1
- 2 collections
- cloud with one leader and several replicas
- in solrconfig.xml: maxWarmingSearchers=1
- no code change
When collection reload using
Hi Jan,
Well, I have very likely confused some old documentation to be up to date, but
all I did was to google for "ExtendedDisMax" and clicked on the first result:
https://wiki.apache.org/solr/ExtendedDisMax
I could only assume that this was a valid page since it belongs to
Hi,
I would like to describe a process we use for overcoming problems in
cluster state when we have networking issues. Would appreciate if anyone
can answer about what are the flaws on this solution and what is the best
practice for recovery in case of network problems involving zookeeper.
I'm
Hmm, if you have some stemming algorithm on that field, [a-z]+works is never
going to work but [a-z]+work should. If the field contains Juniper Networks,
[a-z]+works is not going to be found due to -s being stripped. But if the field
is not tokenized net[a-z]+ is also not going to find
There is nothing wrong with features that appear to be automagical - that
should in fact be a goal for all modern software systems. Of course, there
is no magic, it's all real logic and any magic is purely appearance - it's
just that the underlying logic may be complex and not obvious to an
Hi all.
I’ve been reading through the Suggester component in Solr at
https://cwiki.apache.org/confluence/display/solr/Suggester.
I have a couple of questions regarding it which I haven’t been able to
find the answer for in that page or anywhere else.
Is there a way to get suggestions from
yes. when i search on juniper networks without regex, i can see the results.
But when I search on net[a-z]+ , i could not see juniper networks. i have
looked all the documents in the results, could not find it.
Thank you,
Anil
On 29 February 2016 at 18:42, Markus Jelsma
Hmm, is the field indexed? A field:/[a-z]%2Bwork/ works fine overhere.
Markus
-Original message-
> From:Anil
> Sent: Monday 29th February 2016 13:24
> To: solr-user@lucene.apache.org
> Subject: Re: Solr regex documenation
>
> Yes Markus.
>
> On 29 February 2016 at
On 02/29/2016 07:59 AM, Tom Evans wrote:
On Mon, Feb 29, 2016 at 11:43 AM, David Santamauro
wrote:
You will have noticed below, the field definition does not contain
multiValues=true
What version of the schema are you using? In pre 1.1 schemas,
On Mon, Feb 29, 2016 at 11:43 AM, David Santamauro
wrote:
> You will have noticed below, the field definition does not contain
> multiValues=true
What version of the schema are you using? In pre 1.1 schemas,
multiValued="true" is the default if it is omitted.
Cheers
Hi Katherine, we had exact the same issue, we need to protect our password.
Anyone who can access to solr server can do "ps -elf|grep java" to grep the
solr commandline, and it has all the password in plain text.
The /bin/solr shell will set 10 related system property:
SOLR_SSL_OPTS="
Hi Elaine, Thank for your reply
I did try without grouping then it is working fine. do you have any idea how
we resolve these issue ?
--
View this message in context:
Yes Markus.
On 29 February 2016 at 15:54, Markus Jelsma
wrote:
> Hi - do you enclose the regex in slashes? Do you url encode the + sign?
> Markus
>
>
>
> -Original message-
> > From:Anil
> > Sent: Monday 29th February 2016 7:45
> > To:
Hi Jimi,
I believe you may be confusing some old config and thus was lead to believe
that you need to pre-configure anything in order to start using dismax /
edismax.
In ealier versions of Solr, there was both a named “dismax” as
well as a named “dismax”, setting the defType parameter to
On 02/29/2016 06:05 AM, Mikhail Khludnev wrote:
On Mon, Feb 29, 2016 at 12:43 PM, David Santamauro <
david.santama...@gmail.com> wrote:
unexpected docvalues type SORTED_SET for field 'f1' (expected=SORTED). Use
UninvertingReader or index with docvalues.
DocValues is primary citizen api
A stemmer does not just reduce plurals to their singular forms. It is more
of a rule based approach to reduce a word to its root.
You should try a lemmatizer if you want a more dictionary based approach
although lemmatizers also mostly reduce a word to its root. If you want
only a plural to
Hi Derek,
Why does aggressive stemming worries you? You might have false
positives, but that is desired behavior in most cases. In your case
"iphone" documents will also be returned for "iphon" query. Is this
something that is not desired behavior? You can have more than one field
if you want
On Mon, Feb 29, 2016 at 12:43 PM, David Santamauro <
david.santama...@gmail.com> wrote:
>
> So I started over (deleted all documents), re-deployed configs to
> zookeeper and reloaded the collection.
>
> This error still appears when I group.field=f1
>
> unexpected docvalues type SORTED_SET for
Hi - do you enclose the regex in slashes? Do you url encode the + sign?
Markus
-Original message-
> From:Anil
> Sent: Monday 29th February 2016 7:45
> To: solr-user@lucene.apache.org
> Subject: Re: Solr regex documenation
>
> HI ,
>
> i am using [a-z]+works. i
So I started over (deleted all documents), re-deployed configs to
zookeeper and reloaded the collection.
This error still appears when I group.field=f1
unexpected docvalues type SORTED_SET for field 'f1' (expected=SORTED).
Use UninvertingReader or index with docvalues.
What exactly does
Hi
I am using EnglishMinimalStemFilterFactory to reducewords in plural
forms to singular forms.
The filter factory is not reducingthe plural formof 'es' to the singular
form correctly. It is reducing correctly for plural form of 's'.
"boxes" is reduced to "boxe" instead of "box"
"glasses" to
There is no need to deliberately misinterpret what I wrote. What I was trying
to say was that "automagical" things don't belong in a professional
environment, because it is hiding important information from people. And this
is bad as it is, but if it on top of that is the *intended* meaning for
49 matches
Mail list logo