Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-5953

Analysis not correctly shown when using also HTMLStripCharFilterFactory

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Duplicate
    • 4.7
    • None
    • Admin UI
    • None

    Description

      When analyzing a field with only HTMLStripCharFilterFactory and StandardTokenizerFactory, the analysis page doesn't show output for StandardTokenizerFactory even if json response seems to be correct.

      To reproduce:
      This is the schema:
      <?xml version="1.0" ?>
      <schema name="${solr.core.name}" version="1.5">
      <types>
      <fieldType name="long" class="solr.TrieLongField" precisionStep="0" positionIncrementGap="0"/>
      <fieldType name="testhtml" class="solr.TextField">
      <analyzer>
      <charFilter class="solr.HTMLStripCharFilterFactory"/>
      <tokenizer class="solr.StandardTokenizerFactory"/>
      </analyzer>
      </fieldType>
      <fieldType name="test" class="solr.TextField">
      <analyzer>
      <tokenizer class="solr.StandardTokenizerFactory"/>
      </analyzer>
      </fieldType>
      </types>
      <fields>
      <field name="version" type="long" indexed="true" stored="true"/>
      <field name="id" type="long" indexed="true" stored="true" multiValued="false" />
      <field name="test" type="test" indexed="true" stored="true" multiValued="false" />
      <field name="testhtml" type="testhtml" indexed="true" stored="true" multiValued="false" />
      </fields>
      <!-- field to use to determine and enforce document uniqueness. -->
      <uniqueKey>id</uniqueKey>
      <!-- field for the QueryParser to use when an explicit fieldname is absent -->
      <defaultSearchField>test</defaultSearchField>
      </schema>

      Go to analysis page, choose "testhtml" field and insert "a b" in Field Value (Index).

      The output shown for HTMLSCF is correct ("a b"), but nothing is shown in the output of ST.

      If you choose "test" field, with only ST, it works as expected.

      The json, inspected with firebug, seems correct, I think it is only a graphical issue.

      Attachments

        Issue Links

          Activity

            People

              steffkes Stefan Matheis
              zaccheob Zaccheo Bagnati
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: