[jira] [Comment Edited] (SOLR-12884) Admin UI, admin/luke and *Point fields
[
https://issues.apache.org/jira/browse/SOLR-12884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657963#comment-16657963
]
Christopher Ball edited comment on SOLR-12884 at 10/22/18 11:14 PM:
Could this be an opportunity . . . for Solr to eat its own dog food?
How about using Streaming Expressions - for example the following expression
provides a frequency table for a numeric field:
{code:java}
let (a=search(MyCollection, q=":", fl="myWordCount_l", fq="myWordCount_l:[0 TO
*]", rows=1000, sort="myWordCount_l asc"),
b=col(a, myWordCount_l),
c=freqTable(b)){code}
With the addition of a filter function (either an exponential function or just
a list of step points), it would be on par with the data being provided from
Luke.
@[~joel.bernstein] - thoughts?
was (Author: christopherball):
Could this be an opportunity . . . for Solr to eat its own dog food?
How about using Streaming Expressions - for example the following expression
provides a frequency table for a numeric field:
{code:java}
let (a=search(MyCollection, q=":", fl="myWordCount_l", fq="myWordCount_l:[0 TO
*]", rows=1000, sort="myWordCount_l asc"),
b=col(a, myWordCount_l),
c=freqTable(b)){code}
With the addition of a filter function (either an exponential function or just
a list of step points), it would be on par with the data being provided from
Luke.
@[~joel.bernstein] - thoughts?
> Admin UI, admin/luke and *Point fields
> --
>
> Key: SOLR-12884
> URL: https://issues.apache.org/jira/browse/SOLR-12884
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Affects Versions: master (8.0)
>Reporter: Erick Erickson
>Priority: Major
>
> One of the conference attendees noted that you go to the schema browser and
> click on, say, a pint field, then click "load term info", nothing is shown.
> admin/luke similarly doesn't show much interesting, here's the response for a
> pint .vs. a tint field:
> "popularity":\{ "type":"pint", "schema":"I-SD-OF--"},
> "popularityt":{ "type":"tint", "schema":"I-S--OF--",
> "index":"-TS--", "docs":15},
>
> What, if anything, should we do in these two cases? Since the points-based
> numerics don't have terms like Trie* fields, I don't think we _can_ show much
> more so the above makes sense, it's just jarring to end users and looks like
> a bug.
> WDYT about putting in some useful information though. Say for the Admin UI
> for points-based "terms cannot be shown for points-based fields" or some such?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-12884) Admin UI, admin/luke and *Point fields
[
https://issues.apache.org/jira/browse/SOLR-12884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657963#comment-16657963
]
Christopher Ball edited comment on SOLR-12884 at 10/22/18 11:13 PM:
Could this be an opportunity . . . for Solr to eat its own dog food?
How about using Streaming Expressions - for example the following expression
provides a frequency table for a numeric field:
{code:java}
let (a=search(MyCollection, q=":", fl="myWordCount_l", fq="myWordCount_l:[0 TO
*]", rows=1000, sort="myWordCount_l asc"),
b=col(a, myWordCount_l),
c=freqTable(b)){code}
With the addition of a filter function (either an exponential function or just
a list of step points), it would be on par with the data being provided from
Luke.
@[~joel.bernstein] - thoughts?
was (Author: christopherball):
Could this be an opportunity . . . for Solr to eat its own dog food?
How about using Streaming Expressions - for example the following expression
provides a frequency table for a numeric field:
let (a=search(MyCollection,
q="*:*",
fl="myWordCount_l",
fq="myWordCount_l:[0 TO *]",
rows=1000,
sort="myWordCount_l asc"),
b=col(a, myWordCount_l),
c=freqTable(b))
With the addition of a filter function (either an exponential function or just
a list of step points), it would be on par with the data being provided from
Luke.
@[~joel.bernstein] - thoughts?
> Admin UI, admin/luke and *Point fields
> --
>
> Key: SOLR-12884
> URL: https://issues.apache.org/jira/browse/SOLR-12884
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Affects Versions: master (8.0)
>Reporter: Erick Erickson
>Priority: Major
>
> One of the conference attendees noted that you go to the schema browser and
> click on, say, a pint field, then click "load term info", nothing is shown.
> admin/luke similarly doesn't show much interesting, here's the response for a
> pint .vs. a tint field:
> "popularity":\{ "type":"pint", "schema":"I-SD-OF--"},
> "popularityt":{ "type":"tint", "schema":"I-S--OF--",
> "index":"-TS--", "docs":15},
>
> What, if anything, should we do in these two cases? Since the points-based
> numerics don't have terms like Trie* fields, I don't think we _can_ show much
> more so the above makes sense, it's just jarring to end users and looks like
> a bug.
> WDYT about putting in some useful information though. Say for the Admin UI
> for points-based "terms cannot be shown for points-based fields" or some such?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-12884) Admin UI, admin/luke and *Point fields
[
https://issues.apache.org/jira/browse/SOLR-12884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657963#comment-16657963
]
Christopher Ball edited comment on SOLR-12884 at 10/22/18 3:22 PM:
---
Could this be an opportunity . . . for Solr to eat its own dog food?
How about using Streaming Expressions - for example the following expression
provides a frequency table for a numeric field:
let (a=search(MyCollection,
q="*:*",
fl="myWordCount_l",
fq="myWordCount_l:[0 TO *]",
rows=1000,
sort="myWordCount_l asc"),
b=col(a, myWordCount_l),
c=freqTable(b))
With the addition of a filter function (either an exponential function or just
a list of step points), it would be on par with the data being provided from
Luke.
@[~joel.bernstein] - thoughts?
was (Author: christopherball):
Could this be an opportunity . . . for Solr to eat its own dog food?
How about using Streaming Expressions . . . For example the following
expression provides a frequency table for a numeric field:
let (a=search(MyCollection,
q="*:*",
fl="myWordCount_l",
fq="myWordCount_l:[0 TO *]",
rows=1000,
sort="myWordCount_l asc"),
b=col(a, myWordCount_l),
c=freqTable(b))
With the addition of a filter function (either an exponential function or just
a list of step points), it would be on par with the data being provided from
Luke.
> Admin UI, admin/luke and *Point fields
> --
>
> Key: SOLR-12884
> URL: https://issues.apache.org/jira/browse/SOLR-12884
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Affects Versions: master (8.0)
>Reporter: Erick Erickson
>Priority: Major
>
> One of the conference attendees noted that you go to the schema browser and
> click on, say, a pint field, then click "load term info", nothing is shown.
> admin/luke similarly doesn't show much interesting, here's the response for a
> pint .vs. a tint field:
> "popularity":\{ "type":"pint", "schema":"I-SD-OF--"},
> "popularityt":{ "type":"tint", "schema":"I-S--OF--",
> "index":"-TS--", "docs":15},
>
> What, if anything, should we do in these two cases? Since the points-based
> numerics don't have terms like Trie* fields, I don't think we _can_ show much
> more so the above makes sense, it's just jarring to end users and looks like
> a bug.
> WDYT about putting in some useful information though. Say for the Admin UI
> for points-based "terms cannot be shown for points-based fields" or some such?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-12884) Admin UI, admin/luke and *Point fields
[
https://issues.apache.org/jira/browse/SOLR-12884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657963#comment-16657963
]
Christopher Ball edited comment on SOLR-12884 at 10/20/18 9:58 PM:
---
Could this be an opportunity . . . for Solr to eat its own dog food?
How about using Streaming Expressions . . . For example the following
expression provides a frequency table for a numeric field:
let (a=search(MyCollection,
q="*:*",
fl="myWordCount_l",
fq="myWordCount_l:[0 TO *]",
rows=1000,
sort="myWordCount_l asc"),
b=col(a, myWordCount_l),
c=freqTable(b))
With the addition of a filter function (either an exponential function or just
a list of step points), it would be on par with the data being provided from
Luke.
was (Author: christopherball):
Could this be an opportunity . . . for Solr to eat its own dog food?
How about using Streaming Expressions . . . For example the following
expression would provides a frequency table for a numeric field:
let (a=search(MyCollection,
q="*:*",
fl="myWordCount_l",
fq="myWordCount_l:[0 TO *]",
rows=1000,
sort="myWordCount_l asc"),
b=col(a, myWordCount_l),
c=freqTable(b))
With the addition of an exponential function as a filter, it would be on par
with the data being provided from Luke.
> Admin UI, admin/luke and *Point fields
> --
>
> Key: SOLR-12884
> URL: https://issues.apache.org/jira/browse/SOLR-12884
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Affects Versions: master (8.0)
>Reporter: Erick Erickson
>Priority: Major
>
> One of the conference attendees noted that you go to the schema browser and
> click on, say, a pint field, then click "load term info", nothing is shown.
> admin/luke similarly doesn't show much interesting, here's the response for a
> pint .vs. a tint field:
> "popularity":\{ "type":"pint", "schema":"I-SD-OF--"},
> "popularityt":{ "type":"tint", "schema":"I-S--OF--",
> "index":"-TS--", "docs":15},
>
> What, if anything, should we do in these two cases? Since the points-based
> numerics don't have terms like Trie* fields, I don't think we _can_ show much
> more so the above makes sense, it's just jarring to end users and looks like
> a bug.
> WDYT about putting in some useful information though. Say for the Admin UI
> for points-based "terms cannot be shown for points-based fields" or some such?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
