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

Jan Høydahl edited comment on SOLR-8370 at 10/17/16 6:48 PM:
-------------------------------------------------------------

Looking at author_s, it is broken from Luke. The endpoint 
http://localhost:8983/solr/techproducts/admin/luke does not contain this 
dynamic field (but it contains address_s), neither does while 
http://localhost:8983/solr/techproducts/admin/luke?show=schema but it is listed 
as a copyDest. 

I'm not sure if Luke was supposed to bring it back as a field, but tell us that 
it is a dynField, or whether {{mergeIndexAndSchemaData(index, schema.schema);}} 
method in schema.js was supposed to find out that by itself, as it is now, it 
is that method that populates {{author_s}} but in a partial:true state... It 
also has a line 
{code}
    display.partialState = is.field && !!data.fields[name].partial;
{code}
-which seems to set a variabel but do nothing further with it. So there may be 
some work in progress here that was never finalised? This also smells like a 
new JIRA, not part of this one...-

*UPDATE*: partialState is attempted used in {{schema.html}} but due to a typo, 
it does not work. I will fix that too (use {{display.partialState}} instead of 
just {{partialState}}. That will display a warning box "Because your Index is 
empty, we do not have enough Information about this Field".


was (Author: janhoy):
Looking at author_s, it is broken from Luke. The endpoint 
http://localhost:8983/solr/techproducts/admin/luke does not contain this 
dynamic field (but it contains address_s), neither does while 
http://localhost:8983/solr/techproducts/admin/luke?show=schema but it is listed 
as a copyDest. 

I'm not sure if Luke was supposed to bring it back as a field, but tell us that 
it is a dynField, or whether {{mergeIndexAndSchemaData(index, schema.schema);}} 
method in schema.js was supposed to find out that by itself, as it is now, it 
is that method that populates {{author_s}} but in a partial:true state... It 
also has a line 
{code}
    display.partialState = is.field && !!data.fields[name].partial;
{code}
which seems to set a variabel but do nothing further with it. So there may be 
some work in progress here that was never finalised? This also smells like a 
new JIRA, not part of this one...

> Display Similarity Factory in use in Schema-Browser
> ---------------------------------------------------
>
>                 Key: SOLR-8370
>                 URL: https://issues.apache.org/jira/browse/SOLR-8370
>             Project: Solr
>          Issue Type: Improvement
>          Components: UI
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>            Priority: Trivial
>              Labels: newdev
>             Fix For: 6.3, master (7.0)
>
>         Attachments: SOLR-8370.patch, SOLR-8370.patch, SOLR-8370.patch, 
> SOLR-8370.patch, SOLR-8370.patch, SOLR-8370.patch, screenshot-1.png, 
> screenshot-2.png, screenshot-3.png, screenshot-4.png
>
>
> Perhaps the Admin UI Schema browser should also display which 
> {{<similarity>}} that is in use in schema, like it does per-field.



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

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

Reply via email to