You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder why it is not possible to match text index in documents, that have discriminator map set. ODM always prepends this discriminator map (via the filters) to the query and when you add a match stage in the pipeline, it always fails within the getAggregation() call as the $text stage has to be the first pipeline. Is this by design, is there some workaround or is it a bug?
The text was updated successfully, but these errors were encountered:
From the top of my head it could have been done by an accident: we needed to add filter for the discriminator map and nobody thought about $text restrictions. As a proof of concept you could try forcing automatic discriminator-map-filter to be put as a second stage if $text was used (and only then). Using such approach we will not break any working functionality. If it works then cool, if not we can work from there. :)
I wonder why it is not possible to match text index in documents, that have discriminator map set. ODM always prepends this discriminator map (via the filters) to the query and when you add a match stage in the pipeline, it always fails within the getAggregation() call as the $text stage has to be the first pipeline. Is this by design, is there some workaround or is it a bug?
The text was updated successfully, but these errors were encountered: