Skip to content

Ignore features in FeatureRow if it's not requested in import spec - #101

Merged
feast-ci-bot merged 5 commits into
feast-dev:masterfrom
pradithya:issue_99
Jan 24, 2019
Merged

Ignore features in FeatureRow if it's not requested in import spec#101
feast-ci-bot merged 5 commits into
feast-dev:masterfrom
pradithya:issue_99

Conversation

@pradithya

Copy link
Copy Markdown
Collaborator

Fix #99

@pradithya

Copy link
Copy Markdown
Collaborator Author

/assign @zhilingc
/assign @tims

@zhilingc

Copy link
Copy Markdown
Collaborator

/lgtm

thanks for adding the tests :)

@tims

tims commented Jan 24, 2019

Copy link
Copy Markdown
Contributor

We shouldn't completely ignore them in all these places.

We need errors so that we know what's happening, we don't want to silently discard them.

So what you seem to want is that instead of throwing the whole row into the errors pile, you want to accept as many features as possible and just throw errors for these features.

The only place that needs to do that is the ConvertTypesDoFn. I suggest we should instead emit the row without these suspect features, while also emit an error row (to the errors tag) with just the suspect feature.

If these features proceed past ConvertTypesDoFn, it's a bug, not something we should ignore.

@tims

tims commented Jan 24, 2019

Copy link
Copy Markdown
Contributor

/hold

@zhilingc

Copy link
Copy Markdown
Collaborator

The issue is that they're not necessarily errors. We want to be able to selectively ingest features from a given feature row in the streaming case - similar to how we do it in batch.

@pradithya

Copy link
Copy Markdown
Collaborator Author

I agree, I think we can do it only on ConvertTypesDoFn since it's the most upstream transform.

The only place that needs to do that is the ConvertTypesDoFn. I suggest we should instead emit the row without these suspect features, while also emit an error row (to the errors tag) with just the suspect feature.

Although, I feel emitting error row might not be a good idea since the stream might have a lot of features we are not interested at and it will just flood the error logs.

@feast-ci-bot feast-ci-bot removed the lgtm label Jan 24, 2019
@tims

tims commented Jan 24, 2019

Copy link
Copy Markdown
Contributor

/approve

@tims

tims commented Jan 24, 2019

Copy link
Copy Markdown
Contributor

/hold cancel

@zhilingc

Copy link
Copy Markdown
Collaborator

/approve

@feast-ci-bot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tims, zhilingc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@zhilingc

Copy link
Copy Markdown
Collaborator

/lgtm

@feast-ci-bot
feast-ci-bot merged commit 1691a12 into feast-dev:master Jan 24, 2019
Srihari1192 pushed a commit to Srihari1192/feast that referenced this pull request Apr 15, 2026
….62.0-1775663123

Release: Tekton pipelines → v0.62.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants