Feature/182 add custom query type #183
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These are queries that cannot fit the standard set of `table`, `sql`, `path`.
yruslan
force-pushed
the
feature/182-add-custom-query-type
branch
from
efca387 to
0d9d891
Compare
jirifilip
approved these changes
Apr 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add support for custom queries for data sources (#182).
These are queries that cannot fit the standard set of
table,sql,path.I also included a tiny fix in this PR. Notification email subject was reporting date and time in the system timezone. I've noticed it since on AWS the system timezone is UTC. The fix is to honor the timezone configured in Pramen configuration.