Solr
  1. Solr
  2. SOLR-1022

suggest multiValued for ignored field

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.3
    • Fix Version/s: 1.4
    • Component/s: update
    • Labels:
      None
    • Environment:

      Mac OS 10.5 java 1.5

      Description

      We are actually using the suggested "ignored" field in the schema. I have found, however, that Solr still throws a error 400 if I send in an unmatched multi-valued field.

      It seems that if I set this ignored field to be multiValued than a document with unrecognized single or multiple value fields is sucessfully indexed.

      Attached patch alters this suggested item in the schema.

      1. SOLR-1022.patch
        0.6 kB
        Peter Wolanin

        Activity

        Hide
        Otis Gospodnetic added a comment -

        I must have missed some releated thread on the ML... but can you explan what you mean by "an unmatched multi-valued field"?
        And what does "ignored" field mean? Thanks.

        Show
        Otis Gospodnetic added a comment - I must have missed some releated thread on the ML... but can you explan what you mean by "an unmatched multi-valued field"? And what does "ignored" field mean? Thanks.
        Hide
        Peter Wolanin added a comment -

        The "ignored" field is non-indexed and non-stored. The suggested function in the example schema.xml is to avoid Solr errors when there is a doc field that matches nothing in the schema.

        I found that the one in the example schema being single-valued, if I send in an unmatched multi-valued field I still get the error that enabling this field was intended to prevent.

        I did not send to the ML, since this seemed pretty trivial, but I can do so as well.

        Show
        Peter Wolanin added a comment - The "ignored" field is non-indexed and non-stored. The suggested function in the example schema.xml is to avoid Solr errors when there is a doc field that matches nothing in the schema. I found that the one in the example schema being single-valued, if I send in an unmatched multi-valued field I still get the error that enabling this field was intended to prevent. I did not send to the ML, since this seemed pretty trivial, but I can do so as well.
        Hide
        Hoss Man added a comment -

        good cache peter, that is a bad example ... it was in a DIH example as well so i fixed that too...

        Committed revision 745615.

        Show
        Hoss Man added a comment - good cache peter, that is a bad example ... it was in a DIH example as well so i fixed that too... Committed revision 745615.
        Hide
        Grant Ingersoll added a comment -

        Bulk close for Solr 1.4

        Show
        Grant Ingersoll added a comment - Bulk close for Solr 1.4

          People

          • Assignee:
            Hoss Man
            Reporter:
            Peter Wolanin
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 1h
              1h
              Remaining:
              Remaining Estimate - 1h
              1h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development