Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-24329

Implement Solr search engine prototype using multicore capability to index Content per language

    Details

    • Sprint:
      Pollux Platform S12, Pollux Platform S13

      Description

      At the moment Solr Search Engine indexes Content field data in multivalued fields. This means values from different translations are stored in the same document, in multivalued fields. Because of this no sorting support on field data (Field sort clause) is implemented. Also, having all languages indexed in the same document means relevancy calculation won't be correct.

      Using Solr's multicore/sharding capability to index Content field data per language would enable implementation of Field sort clause while keeping correct document/term statistics per language.

      Search would have to target all/specific cores/shards, depending on the set of languages that need to be searched. Grouping should be used to resolve matches of the same Content (but different language) from the different cores/shards.

      Scope:

      Implement multicore/sharded prototype of the Solr Search Engine, supporting:

      • targeting specific languages (aka field filters parameter)
      • Field sort clause

        Issue Links

          Activity

          Petar Spanja (Inactive) created issue -
          Petar Spanja (Inactive) made changes -
          Field Original Value New Value
          Link This issue relates to EZP-24300 [ EZP-24300 ]
          Petar Spanja (Inactive) made changes -
          Labels candidate-for-next-sprint search solr search solr y2015s12
          Petar Spanja (Inactive) made changes -
          Original Estimate 4 days [ 115200 ]
          Remaining Estimate 4 days [ 115200 ]
          André Rømcke made changes -
          Description At the moment Solr Search Engine indexes Content field data in multivalued fields. This means values from different translations are stored in the same document, in multivalued fields. Because of this no sorting support on field data (Field sort clause) is implemented. Also, having all languages indexed in the same document means relevancy calculation won't be correct.

          Using Solr's multicore/sharding capability to index Content field data per language would enable implementation of Field sort clause while keeping correct document/term statistics per language.

          Search would have to target all/specific cores/shards, depending on the set of languages that need to be searched. Grouping should be used to resolve matches of the same Content (but different language) from the different cores/shards.

          Scope:

          Implement multicore/sharded prototype of the Solr Search Engine, supporting:

          * targeting specific languages (aka field filters parameter)
          * Field sort clause
          At the moment Solr Search Engine indexes Content field data in multivalued fields. This means values from different translations are stored in the same document, in multivalued fields. Because of this no sorting support on field data (Field sort clause) is implemented. Also, having all languages indexed in the same document means relevancy calculation won't be correct.

          Using Solr's multicore/sharding capability to index Content field data per language would enable implementation of Field sort clause while keeping correct document/term statistics per language.

          Search would have to target all/specific cores/shards, depending on the set of languages that need to be searched. Grouping should be used to resolve matches of the same Content (but different language) from the different cores/shards.

          Scope:

          Implement multicore/sharded prototype of the Solr Search Engine, supporting:

          * targeting specific languages (aka field filters parameter)
          * Field sort clause

          _Keep in mind followup is to split out index for Location Search, so getting this to work for Location search on current indexing strategy is not a priority_
          André Rømcke made changes -
          Description At the moment Solr Search Engine indexes Content field data in multivalued fields. This means values from different translations are stored in the same document, in multivalued fields. Because of this no sorting support on field data (Field sort clause) is implemented. Also, having all languages indexed in the same document means relevancy calculation won't be correct.

          Using Solr's multicore/sharding capability to index Content field data per language would enable implementation of Field sort clause while keeping correct document/term statistics per language.

          Search would have to target all/specific cores/shards, depending on the set of languages that need to be searched. Grouping should be used to resolve matches of the same Content (but different language) from the different cores/shards.

          Scope:

          Implement multicore/sharded prototype of the Solr Search Engine, supporting:

          * targeting specific languages (aka field filters parameter)
          * Field sort clause

          _Keep in mind followup is to split out index for Location Search, so getting this to work for Location search on current indexing strategy is not a priority_
          At the moment Solr Search Engine indexes Content field data in multivalued fields. This means values from different translations are stored in the same document, in multivalued fields. Because of this no sorting support on field data (Field sort clause) is implemented. Also, having all languages indexed in the same document means relevancy calculation won't be correct.

          Using Solr's multicore/sharding capability to index Content field data per language would enable implementation of Field sort clause while keeping correct document/term statistics per language.

          Search would have to target all/specific cores/shards, depending on the set of languages that need to be searched. Grouping should be used to resolve matches of the same Content (but different language) from the different cores/shards.

          Scope:

          Implement multicore/sharded prototype of the Solr Search Engine, supporting:

          * targeting specific languages (aka field filters parameter)
          * Field sort clause

          André Rømcke made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          André Rømcke made changes -
          Status Confirmed [ 10037 ] Backlog [ 10000 ]
          André Rømcke made changes -
          Sprint Pollux Platform S12 [ 70 ]
          Sarah Haïm-Lubczanski (Inactive) made changes -
          Labels search solr y2015s12 search solr
          André Rømcke made changes -
          Assignee Petar Spanja [ petar.spanja@ez.no ]
          Petar Spanja (Inactive) made changes -
          Status Backlog [ 10000 ] Development [ 3 ]
          Petar Spanja (Inactive) made changes -
          Link This issue testing discovered EZP-24365 [ EZP-24365 ]
          Petar Spanja (Inactive) made changes -
          Status Development [ 3 ] Development Review [ 10006 ]
          Petar Spanja (Inactive) made changes -
          Original Estimate 4 days [ 115200 ] 0 minutes [ 0 ]
          Petar Spanja (Inactive) made changes -
          Link This issue testing discovered EZP-24375 [ EZP-24375 ]
          Petar Spanja (Inactive) made changes -
          Link This issue testing discovered EZP-24376 [ EZP-24376 ]
          Petar Spanja (Inactive) made changes -
          Link This issue testing discovered EZP-24377 [ EZP-24377 ]
          Petar Spanja (Inactive) made changes -
          Original Estimate 0 minutes [ 0 ] 4 days [ 115200 ]
          Remaining Estimate 4 days [ 115200 ] 0 minutes [ 0 ]
          André Rømcke made changes -
          Rank Ranked higher
          André Rømcke made changes -
          Sprint Pollux Platform S12 [ 70 ] Pollux Platform S12, Pollux Platform S13 [ 70, 72 ]
          André Rømcke made changes -
          Rank Ranked higher
          Petar Spanja (Inactive) made changes -
          Status Development Review [ 10006 ] Development Review done [ 10028 ]
          Petar Spanja (Inactive) made changes -
          Status Development Review done [ 10028 ] Documentation Review done [ 10011 ]
          Rui Silva (Inactive) made changes -
          Status Documentation Review done [ 10011 ] QA [ 10008 ]
          Assignee Petar Spanja [ petar.spanja@ez.no ] Rui Silva [ rui.silva@ez.no ]
          Paulo Nunes (Inactive) made changes -
          Flagged Impediment [ 10000 ]
          Rui Silva (Inactive) made changes -
          Status QA [ 10008 ] InputQ [ 10001 ]
          Assignee Rui Silva [ rui.silva@ez.no ]
          André Rømcke made changes -
          Workflow eZ Engineering Scrumban Workflow [ 67392 ] EZ* Development Workflow [ 69795 ]
          André Rømcke made changes -
          Rank Ranked higher
          Petar Spanja (Inactive) made changes -
          Time Spent 6 hours [ 21600 ]
          Worklog Id 55216 [ 55216 ]
          Petar Spanja (Inactive) made changes -
          Time Spent 6 hours [ 21600 ] 1 day, 4 hours, 30 minutes [ 45000 ]
          Worklog Id 55217 [ 55217 ]
          Petar Spanja (Inactive) made changes -
          Time Spent 1 day, 4 hours, 30 minutes [ 45000 ] 2 days, 2 hours, 45 minutes [ 67500 ]
          Worklog Id 55218 [ 55218 ]
          Petar Spanja (Inactive) made changes -
          Time Spent 2 days, 2 hours, 45 minutes [ 67500 ] 2 days, 5 hours, 30 minutes [ 77400 ]
          Worklog Id 55219 [ 55219 ]
          Petar Spanja (Inactive) made changes -
          Time Spent 2 days, 5 hours, 30 minutes [ 77400 ] 3 days, 2 hours [ 93600 ]
          Worklog Id 55220 [ 55220 ]
          Petar Spanja (Inactive) made changes -
          Time Spent 3 days, 2 hours [ 93600 ] 3 days, 4 hours [ 100800 ]
          Worklog Id 55221 [ 55221 ]
          Petar Spanja (Inactive) made changes -
          Time Spent 3 days, 4 hours [ 100800 ] 3 days, 5 hours, 30 minutes [ 106200 ]
          Worklog Id 55222 [ 55222 ]
          Petar Spanja (Inactive) made changes -
          Time Spent 3 days, 5 hours, 30 minutes [ 106200 ] 3 days, 5 hours, 50 minutes [ 107400 ]
          Worklog Id 55223 [ 55223 ]
          André Rømcke made changes -
          Status InputQ [ 10001 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 69795 ] EZEE Development Workflow [ 124780 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Petar Spanja (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 days
                4d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days, 5 hours, 50 minutes Time Not Required
                3d 5h 50m

                  Agile