[ 
https://issues.apache.org/jira/browse/SOLR-10807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037568#comment-16037568
 ] 

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

Commit 48d16b92734831543b68bb3e28aceb12a3936a70 in lucene-solr's branch 
refs/heads/jira/SOLR-10807 from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=48d16b9 ]

SOLR-10807: add an explicit trie fieldType back to any schema that needs it for 
the 'id' field.

these changes were made with the following quick & dirty script, followed by 
some manual cleanup of 2 schema files
that still use '<types/>' tags *and* use uniqueKey.

if ($_ =~ /name="id"/ and $_ =~ /type="[^"]*(int|float)[^"]*"/) {
    my $type = $1;
    my $class = ($type eq 'int') ? 'solr.TrieIntField' : 'solr.TrieFloatField';
    $_ =~ s/type="[^"]*"/type="nocommit_id_type"/;
    print qq{<fieldType name="nocommit_id_type" class="$class" indexed="true" 
stored="true" multiValued="false" />};
}


>  Randomize PointFields in all tests unless explicit reason not to
> -----------------------------------------------------------------
>
>                 Key: SOLR-10807
>                 URL: https://issues.apache.org/jira/browse/SOLR-10807
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>            Priority: Blocker
>             Fix For: master (7.0)
>
>         Attachments: core.test.log.txt
>
>
> We need to seriously beef up our testing of PointFields to figure out what 
> Solr features don't currently work with PointFields.
> The existing Trie/Point randomization logic in SolrTestCaseJ4 is a good start 
> -- but only a handful of schema files leverage it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to