ression and
> didn't read the full context. I've experienced similar behavior when I've
> deviated (unintentionally) from the documentation. I think it's worth
> raising a JIRA, SEs can definitely benefit from better error
> responses/handling.
>
>
>
&g
ich only
> returns the left stream (first stream param for leftOuterJoin) since there
> is no match.
>
> Hope this helps.
>
> Mathew
>
> On Mon, Feb 27, 2023, 4:25 PM Geren White wrote:
>
> > Hello,
> >
> > When testing out joins in solr streams we
_1: "123",
item_id_2: "456",
item_id: "789",
user_id: "0"
}
Note that the first column in the on clause is from the second table.
Is this expected behavior? We're running solr 8.11.1 and noticed it
while setting up a new query. It's a
t;> http://joelsolr.blogspot.com/
> >>
>
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 |
> http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.c
price_field,0.8)?
>
> Jan
>
> > 28. jun. 2022 kl. 18:58 skrev Geren White :
> >
> > Hello all,
> >
> > I'm wondering if anyone has run into a scenario where they need a
> currency
> > field type with conversion support but also regional pricing
ike to add support
for multiple price types or regional pricing so we were looking at
leveraging payloads. Since payloads are supported through a filter on
TextField and the currency field doesn't support analyzers/filters it
doesn't seem possible.
Anyone run into this and have suggestion
ear. Is there a way to achieve this
> > sorting
> > > without always needing to update the index? E.g. After each specific
> > > duration expires, all documents need to be indexed again for newly
> > > calculated values.This is too much indexing overload. (p.s I am doing
> > > atomic indexing for these fields already)
> >
> >
>
--
*Geren White | Senior Director, Engineering*
*(e)* ge...@1stdibs.com
> >= 500 ….
> > > > >>> else
> > > > >>>
> > > > >>> Simple stuff
> > > > >>>
> > > > >>> fre. 25. jun. 2021 kl. 19:20 skrev Walter Underwood <
> > wun...@wunderwood.org <mailto:wun...@wunderwood.org>>:
> > > > >>>
> > > > >>>> Has anyone implemented protection against deep paging inside
> > Solr? I’m
> > > > >>>> thinking about something like a max_rows parameter, where if
> > start+rows was
> > > > >>>> greater than that, it would limit the max result to that number.
> > Or maybe
> > > > >>>> just return a 400, that would be OK too.
> > > > >>>>
> > > > >>>> I’ve had three or four outages caused by deep paging over the
> > past dozen
> > > > >>>> years with Solr. We implement a limit in the client code, then
> > someone
> > > > >>>> forgets to add it to the redesigned client code. A limit in the
> > request
> > > > >>>> handler would be so much easier.
> > > > >>>>
> > > > >>>> And yes, I know about cursor marks. We don’t want to enable deep
> > paging,
> > > > >>>> we want to stop it.
> > > > >>>>
> > > > >>>> wunder
> > > > >>>> Walter Underwood
> > > > >>>> wun...@wunderwood.org <mailto:wun...@wunderwood.org>
> > > > >>>> http://observer.wunderwood.org/ <
> http://observer.wunderwood.org/>
> > <http://observer.wunderwood.org/ <http://observer.wunderwood.org/>> (my
> > blog)
> > > > >>>>
> > > > >>>> --
> > > > >>> Håvard Wahl Kongsgård
> > > > >>> Data Scientist
> > > > >>
> > > >
> >
> >
>
--
*Geren White | Senior Director, Engineering*
*(e)* ge...@1stdibs.com
