hi Danny,
I didn't mention, but I use calcite 1.21.0.
have attempted to use the function already with no success; it didn't seem
to actually change the provider.
have used the RelMetadataQuery.THREAD_PROVIDERS directly and it worked
perfectly.
i assume it is because the function
The suggested way to set up the RelMetadataProvider is through
RelOptCluster#setMetadataProvider [1]. If you want to customize the
RelMetadataQuery, take the document in RelMetadataQueryBase [2] for a reference.
[1]
thank you it is working great!
On Tue, Jul 21, 2020 at 12:45 AM Stamatis Zampetakis
wrote:
> Hi Taz,
>
> If you are relying on the RelMetadataQuery [1] API then you may need to set
> your provided into THREAD_PROVIDERS in a similar way that it is done in
> RelMetadataTest [2].
>
> Best,
>
Hi Taz,
If you are relying on the RelMetadataQuery [1] API then you may need to set
your provided into THREAD_PROVIDERS in a similar way that it is done in
RelMetadataTest [2].
Best,
Stamatis
[1]
hi,
I am trying to figure out how to add custom logic for providing metadata to
nodes inside my adapter with no luck.
I have an implementation of my own RelMetadataProvider, as described in the
docs.
After looking around, i still couldn't find a way to use this provider in
the planning phase
-
