Antw: Backup And Restore

2016-08-09 Thread Rainer Gnan
Hi Hardika,

the ASG says that a "shared drive" is necessary.
Probably you have to install a NFS server. 

Best regards,
Rainer


--------
Rainer Gnan
Bayerische Staatsbibliothek 
BibliotheksVerbund Bayern
Verbundnahe Dienste
80539 München
Tel.: +49(0)89/28638-2445
Fax: +49(0)89/28638-2665
E-Mail: rainer.g...@bsb-muenchen.de




>>> Hardika Catur S  09.08.2016 09:40 >>>
Hi,

I will create a snapshot on solr backup and restore, but the process 
error and finding errors like this :

org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
Unable to create snapshot directory: 
/root/backup/snapshot.20160809065729143

Please help me to find a solution on.

Thanks,
Hardika CS.



Solr 6.1 :: language specific analysis

2016-08-10 Thread Rainer Gnan
Hello,

I wonder if solr offers a feature (class) to handle different orthogaphy 
versions?
For the German language for example ... in order to find the same documents 
when searching after "Foto" or "Photo".

I appreachiate any help!

Rainer


----
Rainer Gnan
Bayerische Staatsbibliothek 
BibliotheksVerbund Bayern
Verbundnahe Dienste
80539 München
Tel.: +49(0)89/28638-2445
Fax: +49(0)89/28638-2665
E-Mail: rainer.g...@bsb-muenchen.de






Solr 6.1 :: Logging -> WARN FieldTypePluginLoader

2016-08-18 Thread Rainer Gnan
Hi,

after upgrading from "Solr 5.3" to "Solr 6.1" I get  the following logging 
message:

-> WARN true FieldTypePluginLoader TokenFilterFactory is using deprecated 5.2.1 
emulation. You should at some point declare and reindex to at least 6.0,​ 
because 5.x emulation is deprecated and will be removed in 7.0

I could not found relevant information in the web or in other resources in 
order to implement or play out this tip:  You should at some point declare and 
reindex to at least 6.0,​
Neither solrconfig.xml nor schema.xml contains the mentioned Class 
"TokenFilterFactory ".
schema.xml contains only "solr.RemoveDuplicatesToTokenFilterFactory" ... 

Could anybody give me a hint?

I appreciate any help.

Rainer

--------
Rainer Gnan
Bayerische Staatsbibliothek 
BibliotheksVerbund Bayern
Verbundnahe Dienste
80539 München
Tel.: +49(0)89/28638-2445
Fax: +49(0)89/28638-2665
E-Mail: rainer.g...@bsb-muenchen.de






Antw: Re: Solr 6.1 :: Logging -> WARN FieldTypePluginLoader

2016-08-18 Thread Rainer Gnan
... thank you! Great answer. This saved me a lot of time.


Rainer Gnan
Bayerische Staatsbibliothek 
BibliotheksVerbund Bayern
Verbundnahe Dienste
80539 München
Tel.: +49(0)89/28638-2445
Fax: +49(0)89/28638-2665
E-Mail: rainer.g...@bsb-muenchen.de




>>> Shawn Heisey  18.08.2016 15:11 >>>
On 8/18/2016 3:42 AM, Rainer Gnan wrote:
> after upgrading from "Solr 5.3" to "Solr 6.1" I get the following
> logging message: -> WARN true FieldTypePluginLoader TokenFilterFactory
> is using deprecated 5.2.1 emulation. You should at some point declare
> and reindex to at least 6.0,​ because 5.x emulation is
> deprecated and will be removed in 7.0

The "luceneMatchVersion" setting in your solrconfig.xml file is 5.2.1. 
It might also appear in schema.xml, but solrconfig.xml is more likely.

The message is saying "right now, the config settings you're using will
be honored, but they won't be in the future."  This message is a warning
and will not cause Solr to blow up, even in 7.0.

The first thing you'll need to do is change luceneMatchVersion to match
your Solr version -- 6.1.0 -- and reindex.

https://wiki.apache.org/solr/HowToReindex 

Note that this may change how your analyzer chains defined in schema.xml
work.  The change may be obvious, it may be subtle, and in some cases it
might actually make no change at all.  I don't have a list of changes
that are made by different luceneMatchVersion settings.

One thing that luceneMatchVersion will *not* change is index format.  I
mention this because this is a common misconception.  The index format
will be decided by the version of Solr (Lucene) that you're running, not
luceneMatchVersion.

Thanks,
Shawn




How to Debug Solr With Eclipse

2017-07-13 Thread Rainer Gnan
Hello community,

my aim is to develop solr custom code (e.g. UpdateRequestProcessor)
within Eclipse AND to test the code within a debuggable solr/lucene
local instance - also within Eclipse.
Searching the web led me to multiple instructions but for me no one
works.

The only relevant question I actually have to solve this problem is:
Where can I download the source code for the version I want that
includes the ANT build.xml for building an Eclipse-Project?

The solr project page (http://archive.apache.org/dist/lucene/solr/)
seems not to provide that.

I appreciate any hint!

Best regards
Rainer



Antw: Re: How to Debug Solr With Eclipse

2017-07-14 Thread Rainer Gnan
Hi Giovanni,

thank you for this hint!

The whole process (tar -xvf ..., ant compile, ant eclipse) untill importing the 
eclipse-project seems to be fine .
After importing it as an existing eclipse project the project explorer shows an 
error sign on the project folder.
Refreshing does not help.

-> The sub-folder lucene/src is empty ...

I am using eclipse neon, java 1.8.0_112, solr-6.6.0-src.tgz.

Any suggestions?

Cheers,
Rainer

----
Rainer Gnan
Bayerische Staatsbibliothek 
Verbundzentrale des BVB
Referat Verbundnahe Dienste
80807 München
Tel.: +49(0)89/28638-4445
Fax: +49(0)89/28638-2605
E-Mail: rainer.g...@bsb-muenchen.de




>>> Giovanni De Stefano  13.07.2017 19:59 >>>
Hello Rainer,

you have the right link: select the version you want and download the -src 
version.

Once un untar the .tgz you can run `ant eclipse` from the command line and then 
import the generated project in eclipse.

Please note that you will need both and and ivy installed (just start with ant 
eclipse and take it from there: the script will tell you what to do next).

I hope it helps!

Cheers,
Giovanni


> On 13 Jul 2017, at 19:54, govind nitk  wrote:
> 
> Hi,
> 
> Solr has releases, kindly checkout to the needed one.
> 
> 
> cheers
> 
> On Thu, Jul 13, 2017 at 11:20 PM, Rainer Gnan 
> wrote:
> 
>> Hello community,
>> 
>> my aim is to develop solr custom code (e.g. UpdateRequestProcessor)
>> within Eclipse AND to test the code within a debuggable solr/lucene
>> local instance - also within Eclipse.
>> Searching the web led me to multiple instructions but for me no one
>> works.
>> 
>> The only relevant question I actually have to solve this problem is:
>> Where can I download the source code for the version I want that
>> includes the ANT build.xml for building an Eclipse-Project?
>> 
>> The solr project page (http://archive.apache.org/dist/lucene/solr/)
>> seems not to provide that.
>> 
>> I appreciate any hint!
>> 
>> Best regards
>> Rainer
>> 
>> 




Antw: Re: Antw: Re: How to Debug Solr With Eclipse

2017-08-15 Thread Rainer Gnan
Hello Giovanni,

I could not resolve the issue on my workingplace computer.
On my laptop following exactly your steps it works perfectly without warnings 
or else.

But how to start solr correctly within eclipse (oxygen)?

I am navigating to the subdirectory "solr/webapp/web/" an with right-click on 
index.html I select Run as Run with Jetty.
Run Configuration Settings are as follows: 
- WebApp = solr/webapp/web
- Context Path = /solr
- HTTP/HTTPS = 8983

But then I get a half of dozen of Exceptions and solr is unable to start ...
Webbrowser shows a HTTP Error 500 "java.lang.NoSuchMethodError: 
javax.servlet.ServletInputStream.isFinished()Z".
 
What am I doing wrong???

I appreciate any help or hints!
Rainer





--------

Rainer Gnan
Bayerische Staatsbibliothek 
Verbundzentrale des BVB
Referat Verbundnahe Dienste
80807 München
Tel.: +49(0)89/28638-4445

Fax: +49(0)89/28638-2605
E-Mail: rainer.g...@bsb-muenchen.de

>>> Giovanni De Stefano  14.07.17 21.49 Uhr >>>
Hello Rainer,

Have you found the issue?

If not, just to be on the safe side:
1) once you extracted the .tgz you get the folder `solr-6.0.0`, cd in it and 
then just 
2) execute `ant eclipse` and then 
3) in Eclipse do Import -> Existing Projects in the workspace -> select the 
`solr-6.0.0` folder (leave all options the way they are)
4) wait a few minutes…it takes a while to build the whole thing, in the 
meantime it’s normal to see “errors” or “warning”…

I hope it helps,
Giovanni



> On 14 Jul 2017, at 16:01, Rainer Gnan  wrote:
> 
> Hi Giovanni,
> 
> thank you for this hint!
> 
> The whole process (tar -xvf ..., ant compile, ant eclipse) untill importing 
> the eclipse-project seems to be fine .
> After importing it as an existing eclipse project the project explorer shows 
> an error sign on the project folder.
> Refreshing does not help.
> 
> -> The sub-folder lucene/src is empty ...
> 
> I am using eclipse neon, java 1.8.0_112, solr-6.6.0-src.tgz.
> 
> Any suggestions?
> 
> Cheers,
> Rainer
> 
> 
> Rainer Gnan
> Bayerische Staatsbibliothek 
> Verbundzentrale des BVB
> Referat Verbundnahe Dienste
> 80807 München
> Tel.: +49(0)89/28638-4445
> Fax: +49(0)89/28638-2605
> E-Mail: rainer.g...@bsb-muenchen.de
> 
> 
> 
> 
>>>> Giovanni De Stefano  13.07.2017 19:59 >>>
> Hello Rainer,
> 
> you have the right link: select the version you want and download the -src 
> version.
> 
> Once un untar the .tgz you can run `ant eclipse` from the command line and 
> then import the generated project in eclipse.
> 
> Please note that you will need both and and ivy installed (just start with 
> ant eclipse and take it from there: the script will tell you what to do next).
> 
> I hope it helps!
> 
> Cheers,
> Giovanni
> 
> 
>> On 13 Jul 2017, at 19:54, govind nitk  wrote:
>> 
>> Hi,
>> 
>> Solr has releases, kindly checkout to the needed one.
>> 
>> 
>> cheers
>> 
>> On Thu, Jul 13, 2017 at 11:20 PM, Rainer Gnan 
>> wrote:
>> 
>>> Hello community,
>>> 
>>> my aim is to develop solr custom code (e.g. UpdateRequestProcessor)
>>> within Eclipse AND to test the code within a debuggable solr/lucene
>>> local instance - also within Eclipse.
>>> Searching the web led me to multiple instructions but for me no one
>>> works.
>>> 
>>> The only relevant question I actually have to solve this problem is:
>>> Where can I download the source code for the version I want that
>>> includes the ANT build.xml for building an Eclipse-Project?
>>> 
>>> The solr project page (http://archive.apache.org/dist/lucene/solr/)
>>> seems not to provide that.
>>> 
>>> I appreciate any hint!
>>> 
>>> Best regards
>>> Rainer
>>> 
>>> 
> 
> 

0INFO  (main) [] o.e.j.u.log Logging ini or incomplete.
680  INFO  (main) [] o.a.s.s.SolrDispatchFilter  ___  _   Welcome 
to Apache Solr™ version 6.3.0
681  INFO  (main) [] o.a.s.s.SolrDispatchFilter / __| ___| |_ _   Starting 
in standalone mode on port null
681  INFO  (main) [] o.a.s.s.SolrDispatchFilter \__ \/ _ \ | '_|  Install 
dir: null
696  INFO  (main) [] o.a.s.s.SolrDispatchFilter |___/\___/_|_|Start 
time: 2017-08-15T17:03:32.443Z
752  INFO  (main) [] o.a.s.c.SolrResourceLoader solr home defaulted to 
'solr/' (could not find system property or JNDI)
769  INFO  (main) [] o.a.s.c.SolrXmlConfig Loading container configuration 

Solr 6.2.1 :: Collection Aliasing

2016-12-12 Thread Rainer Gnan
Hi,

actually I am trying to use Collection Aliasing in a SolrCloud-environment.

My set up is as follows:

1. Collection_1 (alias "live") linked with config_1
2. Collection_2 (alias "test") linked with config_2
3. Collection_1 is different to Collection _2
4. config_1 is different to config_2 

Case 1: Using
http://hostname.de:8983/solr/Collection_2/select?indent=on&q=*:*&wt=xml&collection=test
leads to the same results as
http://hostname.de:8983/solr/Collection_2/select?indent=on&q=*:*&wt=xml
which is correct.

Case 2: Using
http://hostname.de:8983/solr/Collection_1/select?indent=on&q=*:*&wt=xml&collection=live
leads to the same result as
http://hostname.de:8983/solr/Collection_1/select?indent=on&q=*:*&wt=xml
which is correct, too.

BUT

Case 3: Using
http://hostname.de:8983/solr/Collection_2/select?indent=on&q=*:*&wt=xml&collection=live
leads NOT to the same result as
http://hostname.de:8983/solr/Collection_1/select?indent=on&q=*:*&wt=xml&collection=live
or 
http://hostname.de:8983/solr/Collection_1/select?indent=on&q=*:*&wt=xml

It seems that using alias "live" in case 3 forces solr to search in 
Collection_1 (which is desired) but it uses config_2 of Collection_2 (which is 
not desired).

MY AIM IS:
Running  one collection as productive and the other as test environment within 
a single SolrCloud.
After setting up a new index (new schema, new solrconfig.xml) on the test 
collection I want to asign the test collection the alias "live" and the live 
collection the alias "test".

How can I force solr to search in Collection_X with config_X?

I hope that my description makes clear what my problem is. If not, don't 
hesitate to ask, I appreciate any help.

Rainer





Rainer Gnan
Bayerische Staatsbibliothek 
BibliotheksVerbund Bayern
Verbundnahe Dienste
80539 München
Tel.: +49(0)89/28638-2445
Fax: +49(0)89/28638-2665
E-Mail: rainer.g...@bsb-muenchen.de






Antw: Re: Solr 6.2.1 :: Collection Aliasing

2016-12-12 Thread Rainer Gnan
Hi Shawn,

your workaround works and is exactly what I was looking for.
Did you find this solution via trial and error or can you point me to the 
appropriate section in the APRGuide?

Thanks a lot!
Rainer


Rainer Gnan
Bayerische Staatsbibliothek 
BibliotheksVerbund Bayern
Verbundnahe Dienste
80539 München
Tel.: +49(0)89/28638-2445
Fax: +49(0)89/28638-2665
E-Mail: rainer.g...@bsb-muenchen.de




>>> Shawn Heisey  12.12.2016 11:43 >>>
On 12/12/2016 3:32 AM, Rainer Gnan wrote:
> Hi,
>
> actually I am trying to use Collection Aliasing in a SolrCloud-environment.
>
> My set up is as follows:
>
> 1. Collection_1 (alias "live") linked with config_1
> 2. Collection_2 (alias "test") linked with config_2
> 3. Collection_1 is different to Collection _2
> 4. config_1 is different to config_2 
>
> Case 1: Using
> http://hostname.de:8983/solr/Collection_2/select?indent=on&q=*:*&wt=xml&collection=test
>  
> leads to the same results as
> http://hostname.de:8983/solr/Collection_2/select?indent=on&q=*:*&wt=xml 
> which is correct.
>
> Case 2: Using
> http://hostname.de:8983/solr/Collection_1/select?indent=on&q=*:*&wt=xml&collection=live
>  
> leads to the same result as
> http://hostname.de:8983/solr/Collection_1/select?indent=on&q=*:*&wt=xml 
> which is correct, too.
>
> BUT
>
> Case 3: Using
> http://hostname.de:8983/solr/Collection_2/select?indent=on&q=*:*&wt=xml&collection=live
>  
> leads NOT to the same result as
> http://hostname.de:8983/solr/Collection_1/select?indent=on&q=*:*&wt=xml&collection=live
>  
> or 
> http://hostname.de:8983/solr/Collection_1/select?indent=on&q=*:*&wt=xml 

Do the query this way:

http://hostname.de:8983/solr/live/select?indent=on&q=*:* 

I have no idea whether the behavior you are seeing is correct or wrong,
but if you send the traffic directly to the alias it should work correctly.

It might turn out that this is a bug, but I believe the above workaround
should take care of the issue in your environment.

Thanks,
Shawn