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
Is your feature request related to a problem? Please describe.
Long term solution to #3708 : Don't build transformations for every pull query on the same state store but rather built them only the first time.
The approach followed by the above PR is to create the transformation only the first time they are requested via the use of a memoized supplier. A longer term solution would be to build the code once, when building the initial CTAS query.
Describe the solution you'd like
Pull the queryId out of the mappers and filters etc, so that it can be passed in as a parameter when being executed. This would allow us to create the baked code as we're building the source aggregate query, i.e. rather than build the materialization, and cache it, on first use, we just build it when building the source aggregate query and store it, rather than the provider, in the query metadata.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Long term solution to #3708 : Don't build transformations for every pull query on the same state store but rather built them only the first time.
The approach followed by the above PR is to create the transformation only the first time they are requested via the use of a memoized supplier. A longer term solution would be to build the code once, when building the initial CTAS query.
Describe the solution you'd like
Pull the queryId out of the mappers and filters etc, so that it can be passed in as a parameter when being executed. This would allow us to create the baked code as we're building the source aggregate query, i.e. rather than build the materialization, and cache it, on first use, we just build it when building the source aggregate query and store it, rather than the provider, in the query metadata.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: