Hi @Agent007. Thanks for your PR.

I'm waiting for a feast-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Codecov Report

Merging #2002 (c655d1b) into master (63680ba) will decrease coverage by 0.02%.
The diff coverage is 78.72%.

@@            Coverage Diff             @@
##           master    #2002      +/-   ##
==========================================
- Coverage   83.23%   83.20%   -0.03%     
==========================================
  Files         103      103              
  Lines        8421     8467      +46     
==========================================
+ Hits         7009     7045      +36     
- Misses       1412     1422      +10     

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 63680ba...c655d1b. Read the comment docs.

/ok-to-test

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adchia, Agent007

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

The pull request process is described here

@adchia In addition to the aforementioned RedShift-related errors, I now see errors related to tracing_span() after rebasing the latest from the main branch. I thought FEAST_USAGE is False in the integration test environment, so I don't see how tracing_span() would raise its RuntimeError if _is_enabled is supposed to be False.
Also, FYI, in order for make test-python-universal-local pass, I added checks in test_feature_get_online_features_types_match() to see if feature is not None before making the assertions on the expected feature types. Did you intend to handle None features differently?

@adchia , I think your integration test environment's RedShift instance may need to be updated to recognize the SUPER data type. The RedShift-based integration tests are failing because the example test data containing array types aren't able to be saved in RedShift...

Might it be simpler to change the tests used for verifying this PR to avoid this and open a separate PR to add a test for SUPER columns? Just conscious that this ODFV list feature applies to ALL offline + online stores so not sure it makes sense to block on Redshift.

Might get both merged faster too.

yep agreed with @judahrand . The main thing preventing the merge is now #2007 going in. We also had a fix for the tracing span bug that already win.

@judahrand Apologies for the delay. I'm juggling other tasks at work currently. Please feel free to add onto this PR branch if this is urgent for you.

/lgtm