-
Notifications
You must be signed in to change notification settings - Fork 13.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add week time grain for Elasticsearch datasets #25683
Merged
john-bodley
merged 4 commits into
apache:master
from
mikelv92:add-week-time-grain-for-elasticsearch
Oct 19, 2023
Merged
Changes from 3 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
54 changes: 54 additions & 0 deletions
54
tests/integration_tests/db_engine_specs/elasticsearch_tests.py
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
# Licensed to the Apache Software Foundation (ASF) under one | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Woot! Thanks for adding a test. |
||
# or more contributor license agreements. See the NOTICE file | ||
# distributed with this work for additional information | ||
# regarding copyright ownership. The ASF licenses this file | ||
# to you under the Apache License, Version 2.0 (the | ||
# "License"); you may not use this file except in compliance | ||
# with the License. You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, | ||
# software distributed under the License is distributed on an | ||
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY | ||
# KIND, either express or implied. See the License for the | ||
# specific language governing permissions and limitations | ||
# under the License. | ||
from sqlalchemy import column | ||
|
||
from superset.db_engine_specs.elasticsearch import ElasticSearchEngineSpec | ||
from tests.integration_tests.db_engine_specs.base_tests import TestDbEngineSpec | ||
|
||
|
||
class TestElasticsearchDbEngineSpec(TestDbEngineSpec): | ||
def test_timegrain_week_expression(self): | ||
""" | ||
mikelv92 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
DB Eng Specs (elasticsearch): Test time grain expressions | ||
""" | ||
col = column("ts") | ||
test_cases = { | ||
mikelv92 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
"date": "DATE_TRUNC('week', ts)", | ||
"date_nanos": "DATE_TRUNC('week', ts)", | ||
} | ||
for type_, expected in test_cases.items(): | ||
col.type = type_ | ||
actual = ElasticSearchEngineSpec.get_timestamp_expr( | ||
col=col, pdf=None, time_grain="P1W" | ||
) | ||
self.assertEqual(str(actual), expected) | ||
|
||
def test_timegrain_hour_expression(self): | ||
""" | ||
DB Eng Specs (elasticsearch): Test time grain expressions | ||
""" | ||
col = column("ts") | ||
test_cases = { | ||
"date": "HISTOGRAM(ts, INTERVAL 1 HOUR)", | ||
"date_nanos": "HISTOGRAM(ts, INTERVAL 1 HOUR)", | ||
} | ||
for type_, expected in test_cases.items(): | ||
col.type = type_ | ||
actual = ElasticSearchEngineSpec.get_timestamp_expr( | ||
col=col, pdf=None, time_grain="PT1H" | ||
) | ||
self.assertEqual(str(actual), expected) |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we using
DATE_TRUNC
and notHISTOGRAM
? Ideally it would be great if these were consistent.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
HISTOGRAM
groups the data byINTERVAL
but there is no "week" interval in Elasticsearch.Perhaps there is a refactor needed to use
DATE_TRUNC
for the other time grains as well? I could do it, but as I am new to this community, could you let me know if I should do it in this PR or open a separate one for refactoring? 😄There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mikelv92 thanks for the explanation. I think it's ok to merge this PR as is, but if you're interested in doing a fast follow to change all the existing time grains to use
DATE_TRUNC
—which seems to be the blessed option—that would be great.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@john-bodley Here is the follow-up PR: #25717