Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-8797

Make fulltext normalization algorithm configurable

    Details

    • Impact type:
      Configuration format change
    • Upgrade notes:
      Hide

      To customizing splitting/parsing, a repository config can now specify a custom fulltext parser class using:

      <fulltext analyzer="..." parser="some.parser.class" ...>

      where some.parser.class must be a subclass of org.nuxeo.ecm.core.storage.sql.FulltextParser. It's likely that implementors will want to override method parse().

      Show
      To customizing splitting/parsing, a repository config can now specify a custom fulltext parser class using: <fulltext analyzer="..." parser="some.parser.class" ...> where some.parser.class must be a subclass of org.nuxeo.ecm.core.storage.sql.FulltextParser. It's likely that implementors will want to override method parse().

      Description

      The way the strings are split and passed to the database for fulltext indexing should be made more configurable.
      Today in 5.5 there's just the property org.nuxeo.vcs.fulltext.wordsplit which is used for split.
      This should be a full-blown configurable class.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.