Grokbase Groups Lucene dev June 2016
FAQ
[ https://issues.apache.org/jira/browse/SOLR-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Rowe reopened SOLR-9004:
------------------------------

Reopening to backport to 5.6 and 5.5.2.
films example's name field is created multiValued despite FAQ
-------------------------------------------------------------

Key: SOLR-9004
URL: https://issues.apache.org/jira/browse/SOLR-9004
Project: Solr
Issue Type: Bug
Affects Versions: 6.0
Reporter: Alexandre Rafalovitch
Assignee: Varun Thacker
Priority: Minor
Fix For: 6.0.1, 6.1, master (7.0)


In the README.txt for the *films* example, it says:
bq. Without overriding those field types, the _name_ field would have been guessed as a multi-valued string field type .... it makes more sense with this
particular data set domain to have the movie name be a single valued general full-text searchable field,
However, the actual Schema API call does not specify multiValued=false, just that it is of *text_general* type. That type is defined as multiValued, so the end result is multiValued as well, opposite to the explanation given.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org

Search Discussions

  • ASF subversion and git services (JIRA) at Jun 17, 2016 at 8:22 pm
    [ https://issues.apache.org/jira/browse/SOLR-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336857#comment-15336857 ]

    ASF subversion and git services commented on SOLR-9004:
    -------------------------------------------------------

    Commit 276edf3640b065017086bf6a22c1800f9c7eaf3c in lucene-solr's branch refs/heads/branch_5_5 from [~varunthacker]
    [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=276edf3 ]

    SOLR-9004: Fix name field type definition in films example

    films example's name field is created multiValued despite FAQ
    -------------------------------------------------------------

    Key: SOLR-9004
    URL: https://issues.apache.org/jira/browse/SOLR-9004
    Project: Solr
    Issue Type: Bug
    Affects Versions: 6.0
    Reporter: Alexandre Rafalovitch
    Assignee: Varun Thacker
    Priority: Minor
    Fix For: 5.6, 6.0.1, 6.1, 5.5.2, master (7.0)


    In the README.txt for the *films* example, it says:
    bq. Without overriding those field types, the _name_ field would have been guessed as a multi-valued string field type .... it makes more sense with this
    particular data set domain to have the movie name be a single valued general full-text searchable field,
    However, the actual Schema API call does not specify multiValued=false, just that it is of *text_general* type. That type is defined as multiValued, so the end result is multiValued as well, opposite to the explanation given.


    --
    This message was sent by Atlassian JIRA
    (v6.3.4#6332)

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
    For additional commands, e-mail: dev-help@lucene.apache.org
  • ASF subversion and git services (JIRA) at Jun 17, 2016 at 8:22 pm
    [ https://issues.apache.org/jira/browse/SOLR-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336858#comment-15336858 ]

    ASF subversion and git services commented on SOLR-9004:
    -------------------------------------------------------

    Commit 13ed5de600408e13936174620fec6404156b1771 in lucene-solr's branch refs/heads/branch_5_5 from [~steve_rowe]
    [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=13ed5de ]

    SOLR-9004: Add 5.5.2 CHANGES entry

    films example's name field is created multiValued despite FAQ
    -------------------------------------------------------------

    Key: SOLR-9004
    URL: https://issues.apache.org/jira/browse/SOLR-9004
    Project: Solr
    Issue Type: Bug
    Affects Versions: 6.0
    Reporter: Alexandre Rafalovitch
    Assignee: Varun Thacker
    Priority: Minor
    Fix For: 5.6, 6.0.1, 6.1, 5.5.2, master (7.0)


    In the README.txt for the *films* example, it says:
    bq. Without overriding those field types, the _name_ field would have been guessed as a multi-valued string field type .... it makes more sense with this
    particular data set domain to have the movie name be a single valued general full-text searchable field,
    However, the actual Schema API call does not specify multiValued=false, just that it is of *text_general* type. That type is defined as multiValued, so the end result is multiValued as well, opposite to the explanation given.


    --
    This message was sent by Atlassian JIRA
    (v6.3.4#6332)

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
    For additional commands, e-mail: dev-help@lucene.apache.org
  • ASF subversion and git services (JIRA) at Jun 17, 2016 at 8:22 pm
    [ https://issues.apache.org/jira/browse/SOLR-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336859#comment-15336859 ]

    ASF subversion and git services commented on SOLR-9004:
    -------------------------------------------------------

    Commit d216ce293b1f0d3ffb1af59797f1d001c49b8327 in lucene-solr's branch refs/heads/branch_5x from [~varunthacker]
    [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d216ce2 ]

    SOLR-9004: Fix name field type definition in films example

    films example's name field is created multiValued despite FAQ
    -------------------------------------------------------------

    Key: SOLR-9004
    URL: https://issues.apache.org/jira/browse/SOLR-9004
    Project: Solr
    Issue Type: Bug
    Affects Versions: 6.0
    Reporter: Alexandre Rafalovitch
    Assignee: Varun Thacker
    Priority: Minor
    Fix For: 5.6, 6.0.1, 6.1, 5.5.2, master (7.0)


    In the README.txt for the *films* example, it says:
    bq. Without overriding those field types, the _name_ field would have been guessed as a multi-valued string field type .... it makes more sense with this
    particular data set domain to have the movie name be a single valued general full-text searchable field,
    However, the actual Schema API call does not specify multiValued=false, just that it is of *text_general* type. That type is defined as multiValued, so the end result is multiValued as well, opposite to the explanation given.


    --
    This message was sent by Atlassian JIRA
    (v6.3.4#6332)

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
    For additional commands, e-mail: dev-help@lucene.apache.org
  • Steve Rowe (JIRA) at Jun 17, 2016 at 8:22 pm
    [ https://issues.apache.org/jira/browse/SOLR-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Steve Rowe resolved SOLR-9004.
    ------------------------------
            Resolution: Fixed
         Fix Version/s: 5.5.2
                        5.6
    films example's name field is created multiValued despite FAQ
    -------------------------------------------------------------

    Key: SOLR-9004
    URL: https://issues.apache.org/jira/browse/SOLR-9004
    Project: Solr
    Issue Type: Bug
    Affects Versions: 6.0
    Reporter: Alexandre Rafalovitch
    Assignee: Varun Thacker
    Priority: Minor
    Fix For: 5.6, 5.5.2, master (7.0), 6.1, 6.0.1


    In the README.txt for the *films* example, it says:
    bq. Without overriding those field types, the _name_ field would have been guessed as a multi-valued string field type .... it makes more sense with this
    particular data set domain to have the movie name be a single valued general full-text searchable field,
    However, the actual Schema API call does not specify multiValued=false, just that it is of *text_general* type. That type is defined as multiValued, so the end result is multiValued as well, opposite to the explanation given.


    --
    This message was sent by Atlassian JIRA
    (v6.3.4#6332)

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
    For additional commands, e-mail: dev-help@lucene.apache.org

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdev @
categorieslucene
postedJun 17, '16 at 8:19p
activeJun 17, '16 at 8:22p
posts5
users1
websitelucene.apache.org

1 user in discussion

Steve Rowe (JIRA): 5 posts

People

Translate

site design / logo © 2019 Grokbase