order of things, and since I will be using the export
handler, it will use docValues anyways and lose the order.
So is there any case that I need stored=true?
Best,
ufuk
--
uyilmaz
false, docValues=true
> 3) indexed=false, stored=false, docValues=true
>
> What would be the performance implications for these options?
>
> Best,
> Wei
--
uyilmaz
ly not the same
with what I'm looking for. It gives the words occuring frequently in the result
set, but not occuring as frequently outside it. So it's better to find out
frequency anomalies rather than simply the counts.
Do you have any suggestions?
Regards
--
uyilmaz
Sorry, correction, taking "the" time
On Mon, 19 Oct 2020 22:18:30 +0300
uyilmaz wrote:
> Thanks for taking time to write a detailed answer.
>
> We use Solr to both store our data and to perform aggregations, using
> faceting or streaming expressions. When required anal
d=false stored=false
docValues=true) right?
--uyilmaz
On Mon, 19 Oct 2020 14:14:27 -0400
Michael Gibney wrote:
> As you've observed, it is indeed possible to facet on fields with
> docValues=true, indexed=false; but in almost all cases you should
> probably set indexed=true. 1. for
;
> DocValues is a different way to index/store values. Faceting is a
> primary use case where docValues are better than what 'indexed=true'
> gives you.
>
> Regards,
>Alex.
>
> On Mon, 19 Oct 2020 at 12:51, uyilmaz wrote:
> >
> >
> > H
Hey all,
>From my little experiments, I see that (if I didn't make a stupid mistake) we
>can facet on fields marked as both indexed and stored being false:
I'm suprised by this, I thought I would need to index it. Can you confirm this?
Regards
--
uyilmaz
is going on. 2 collections
seem to be in recovery, can recovery cause this behavior?
Regards and have a nice day
--
uyilmaz
oelsolr.blogspot.com/
>
>
> On Tue, Oct 13, 2020 at 6:30 PM uyilmaz wrote:
>
> > I think I found the reason right after asking (facepalm), but it took me
> > days to realize this.
> >
> > I think fetch performs a naive "in" query, something like:
&g
Thank you!
On Wed, 14 Oct 2020 09:41:16 +0200
Szűcs Roland wrote:
> Hi,
> I got it from the solr user list.
>
>
> Roland
>
> uyilmaz ezt írta (időpont: 2020. okt. 14.,
> Sze, 9:39):
>
> > Hello all,
> >
> > I have never got an answer to my q
Hello all,
I have never got an answer to my questions in this mailing list yet, and my
mail client shows INVALID next to my mail address, so I thought I should check
if my emails are reaching to you.
Can anyone reply?
Regards
--
uyilmaz
umed it would work.
Sorry to take your time, I hope this helps somebody later.
Have a nice day.
On Wed, 14 Oct 2020 00:38:05 +0300
uyilmaz wrote:
>
> Hi all,
>
> I have a streaming expression looking like:
>
> fetch(
> myAlias,
> top(
> n=3,
> v
ias,
top(
n=2,
various expressions here
sort="count(*) desc"
),
fl="username", on="userid=userid", batchSize=2
)
Result is:
{
"result-set":{
"docs":[{
"userid":"123123",
"count(*)":58,
"username":"mura"}
,{
"userid":"123123123",
"count(*)":32,
"username":"Ayha"}
,{
"EOF":true,
"RESPONSE_TIME":34889}]}}
What can be the problem?
Regards
~~ufuk
--
uyilmaz
of seconds. Do you see this behavior
too? Is it intentional?
I usually use Postman for querying so this is not a problem most of the time,
but I just wanted to see streaming expression explanation diagrams.
Have a nice day~~
--
uyilmaz
eater than 1.
~Regards
--
uyilmaz
rameter exactly the same way, using:
String collectionName = factory.getValueOperand(expression, 0)
I'm lost. When I use an alias in place of multiple collections it works as
desired, but we have many collections and queries are generated dynamically so
we would need many combination of aliases.
Need help.
Regards
--
uyilmaz
16 matches
Mail list logo
