[Koha] Elasticsearch setup

[Tom Hanstra]

Hmm. I did wonder about that. I am running Elasticsearch 6 but maybe it is
getting ready for 7?  Or does it think I'm still running 7.

What version of Elasticsearch is known to work?

Tom

On Fri, Mar 20, 2020 at 9:27 AM Jonathan Druart <
jonathan.druart at bugs.koha-community.org> wrote:

> Tom,
>
> The error is bad, I guess it comes from get_all_biblios_iterator.
> What are you developer skill? I'd try to know if it comes from wrong/bad
> data from a record, or something else.
>
> It seems that you are back to version 7 ("To be compatible with 7.0..." in
> the logs)?
>
> You can certainly ignore the warnings.
>
>
> Le ven. 20 mars 2020 à 13:45, Tom Hanstra <hanstra at nd.edu> a écrit :
>
>> Anyone have further ideas on this. I'm close to giving up on
>> Elasticsearch for this year's iteration unless I can figure out how to get
>> this working.
>>
>> Thanks,
>> Tom
>>
>> On Wed, Mar 18, 2020 at 1:01 PM Tom Hanstra <hanstra at nd.edu> wrote:
>>
>>> The "Search Engine" portion of the Administration pages shows my search
>>> engine as Elasticsearch with MARC format of ISO2709.
>>>
>>> About Koha shows:
>>> Nodes: localhost:9200 | Status: running | Indices:
>>> koha_london_test_biblios (count: 12294), koha_london_test_authorities
>>> (count: 6163)
>>>
>>> and no errors there.
>>>
>>> As mentioned, my indices are:
>>>
>>> curl http://localhost:9200/_cat/indices
>>> yellow open koha_london_test_biblios     -Egm0TdKR6KXFcOZQhgoBA 5 1
>>> 12294 0 67.1mb 67.1mb
>>> yellow open koha_london_test_authorities vWlrnM6USHaXmpokR-UV-Q 5 1
>>>  6163 0  4.5mb  4.5mb
>>>
>>> And the lines in my koha-conf.xml file:
>>>
>>> <elasticsearch>
>>>      <server>localhost:9200</server>
>>>      <index_name>koha_london_test</index_name>
>>>
>>>      <!-- See https://metacpan.org/pod/Search::Elasticsearch#cxn_pool
>>> -->
>>>      <cxn_pool>Static</cxn_pool>
>>>  </elasticsearch>
>>>
>>> Not sure what the cxn_pool setting does. But the index_name in the
>>> config file matches up with both the koha-conf file and the information
>>> seen in About Koha.
>>>
>>> When building the indexes, I get the following:
>>>
>>> PERL5LIB=/usr/share/koha/lib:/usr/local/lib:/usr/local/share/perl5
>>> ./bin/search_tools/rebuild_elasticsearch.pl -v
>>> [6267] Checking state of biblios index
>>> DEPRECATION] [types removal] Specifying types in put mapping requests is
>>> deprecated. To be compatible with 7.0, the mapping definition should not be
>>> nested under the type name, and the parameter include_type_name must be
>>> provided and set to false. (and much more)
>>> [6267] Checking state of authorities index
>>> - Similar deprecation warning
>>>
>>> Then the indexing continues until I get a few:
>>>
>>> No record passed at /usr/share/koha/lib/Koha/MetadataIterator.pm line 71.
>>> Something went wrong reading record for biblio
>>> Koha::Schema::Result::Biblio=HASH(0xfed8a88)->biblionumber: Can't bless
>>> non-reference value at /usr/share/koha/lib/Koha/BiblioUtils.pm line 70.
>>>
>>> And then indexing pretty much completes without further complaints.
>>>
>>> But searches are not finding any records when searching. The current
>>> errors in the koha error log from a search include:
>>>
>>> Wed Mar 18 16:57:32.008173 2020] [cgi:error] [pid 2672] [client
>>> 127.0.0.1:44184] AH01215: [Wed Mar 18 16:57:32 2020] opac-search.pl:
>>> Use of uninitialized value $f in pattern match (m//) at
>>> /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/QueryBuilder.pm line
>>> 725.: /usr/share/koha/opac/cgi-bin/opac/opac-search.pl, referer:
>>> https://london-test.library.nd.edu/cgi-bin/koha/opac-search.pl?idx=&q=bible
>>> [Wed Mar 18 16:57:32.008304 2020] [cgi:error] [pid 2672] [client
>>> 127.0.0.1:44184] AH01215: [Wed Mar 18 16:57:32 2020] opac-search.pl:
>>> Use of uninitialized value $f in exists at
>>> /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/QueryBuilder.pm line
>>> 729.: /usr/share/koha/opac/cgi-bin/opac/opac-search.pl, referer:
>>> https://london-test.library.nd.edu/cgi-bin/koha/opac-search.pl?idx=&q=bible
>>>
>>> Any thoughts on what might be uninitialized and how to fix it?
>>>
>>> Thanks again,
>>> Tom
>>>
>>

-- 
*Tom Hanstra*
*Sr. Systems Administrator*
hanstra at nd.edu