[DO NOT MERGE] DEMO fix(time_comparison):Use Join queries when using time comparison #27853
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
To facilitate the discussion related our experimental feature for time comparison, we're extracting out form the original PR all the back end changes related to how to create left outer join queries when time comparison is needed. Using JOIN statement would help tackling issues related to
Row Limit
discussed in this issue. Right now we are raising an exception message to users that try to generate these joined queries on databases where JOINs are not supported.Known limitations:
time_offset
property in theQueryObject
, meaning that it's not compatible with existing API that allows for multiple ranges using such property.time_offset
API that applies the joins on DataFrame levelBEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION