-
Notifications
You must be signed in to change notification settings - Fork 44
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
[HOPSWORKS-2134] Extend Query constructor with filter capability #174
Conversation
084c525
to
ca66a4f
Compare
50b69b1
to
043fcff
Compare
|
||
|
||
class FeatureGroup(feature_group_base.FeatureGroupBase): | ||
class FeatureGroupBase: |
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.
I don't understand this refactor. Why putting everything on a single file?
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.
I am not a huge fan either, but somehow I was getting circular imports because I created the new constructor
package. It's quite a pain to debug those, so I can try and find a different solution, but this was the most obvious fix.
docs/templates/query_vs_dataframe.md
Outdated
```python | ||
# create a query | ||
feature_join = rain_fg.select_all() | ||
.join(temperature_fg.select_all(), on=["date", "location_id"]) |
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.
I'd keep this first example simple and also mention how the joining key is selected.
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.
added more examples also with scala equivalents.
Moving feature groups into single module to resolve circular imports.
Also moving all query constructor related classes into separate package.