Grokbase Groups Lucene dev June 2016
[ ]

ASF subversion and git services commented on SOLR-9004:

Commit 276edf3640b065017086bf6a22c1800f9c7eaf3c in lucene-solr's branch refs/heads/branch_5_5 from [~varunthacker]
[;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
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

To unsubscribe, e-mail:
For additional commands, e-mail:

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 5 | next ›
Discussion Overview
groupdev @
postedJun 17, '16 at 8:19p
activeJun 17, '16 at 8:22p

1 user in discussion

Steve Rowe (JIRA): 5 posts



site design / logo © 2019 Grokbase