uery time the hierarchy would
> change say Steps -> Interactions -> Customers (to use your analogy) if
> filtering needed for (a leaf) object specific attribute.
>
> Norbert
>
> On Tue, 4 May 2021 at 21:01, Timothy Potter wrote:
>
> > Did you try routing all docs f
It sounds like nobody knows. Just one last try. Up !
Tx
On 2021/04/21 10:08:16, Alain Rogister wrote:
> Hi,
>
> Imagine that you have been tasked with designing a Solr-based system that
> indexes and queries data aggregated from several relational databases. All
> the
deeper
> > https://lucidworks.com/post/solr-and-joins/
> >
> > Good luck
> >
> > On Wed, 21 Apr 2021, 13:55 Alain Rogister, wrote:
> >
> > > Hi,
> > >
> > > Imagine that you have been tasked with designing a Solr-based system that
> &g
ustomer ID)
>
> Tim
>
> On Thu, Apr 22, 2021 at 1:55 PM Eran Buchnick wrote:
> >
> > Read this before going deeper
> > https://lucidworks.com/post/solr-and-joins/
> >
> > Good luck
> >
> > On Wed, 21 Apr 2021, 13:55 Alain Rogister, wrote:
> &g
nsive example matching my own
anywhere. Let's hope some brave soul steps in !
On 2021/04/22 19:54:38, Eran Buchnick wrote:
> Read this before going deeper
> https://lucidworks.com/post/solr-and-joins/
>
> Good luck
>
> On Wed, 21 Apr 2021, 13:55 Alain Rogister, wrote:
>
Hi,
Imagine that you have been tasked with designing a Solr-based system that
indexes and queries data aggregated from several relational databases. All the
data items are ultimately related to a common object type, so the logical data
schema looks like :
Customer
Profile
Events
