Bug 22256 - llength mapping wrong in default Elasticsearch mappings
Summary: llength mapping wrong in default Elasticsearch mappings
Status: RESOLVED DUPLICATE of bug 22339
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Elasticsearch (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor
Assignee: Ere Maijala
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-01 12:20 UTC by Ere Maijala
Modified: 2019-03-14 11:24 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Bug 22256: Fix lleader mapping in Elasticsearch (1.06 KB, patch)
2019-02-01 13:18 UTC, Ere Maijala 		Details | Diff | Splinter Review
Bug 22256: Fix llength mapping in Elasticsearch (1.07 KB, patch)
2019-02-01 15:24 UTC, Ere Maijala 		Details | Diff | Splinter Review
Bug 22256: Fix llength mapping in Elasticsearch (1.12 KB, patch)
2019-03-05 11:54 UTC, Josef Moravec 		Details | Diff | Splinter Review
Show Obsolete (2) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ere Maijala 2019-02-01 12:20:10 UTC 
lleader is set to come from positions 1-5 while it should be 0-4.
Comment 1 Ere Maijala 2019-02-01 13:18:58 UTC 
Created attachment 84609 [details] [review]
Bug 22256: Fix lleader mapping in Elasticsearch

Test plan:
1. Reset mappings
2. Index records
3. Check that in Elasticsearch the correct length information is stored
Comment 2 Ere Maijala 2019-02-01 15:24:32 UTC 
Created attachment 84630 [details] [review]
Bug 22256: Fix llength mapping in Elasticsearch

Test plan:
1. Reset mappings
2. Index records
3. Check that in Elasticsearch the correct length information is stored in llength
Comment 3 Josef Moravec 2019-03-05 11:54:20 UTC 
Created attachment 86058 [details] [review]
Bug 22256: Fix llength mapping in Elasticsearch

Test plan:
1. Reset mappings
2. Index records
3. Check that in Elasticsearch the correct length information is stored in llength

Signed-off-by: Josef Moravec <josef.moravec@gmail.com>
Comment 4 Ere Maijala 2019-03-14 11:24:11 UTC 
I'm incorporating this to other similar fixes in bug 22339, which also gets an update script.

*** This bug has been marked as a duplicate of bug 22339 ***