Title: Consolidate document retrieval methods: Remove v1 and standardize on v2 · Issue #5537 · feast-dev/feast · GitHub
Open Graph Title: Consolidate document retrieval methods: Remove v1 and standardize on v2 · Issue #5537 · feast-dev/feast
X Title: Consolidate document retrieval methods: Remove v1 and standardize on v2 · Issue #5537 · feast-dev/feast
Description: Problem Statement Currently, Feast has both v1 and v2 document retrieval methods (retrieve_online_documents_v1 and retrieve_online_documents_v2) across different online stores. This creates inconsistency and maintenance overhead. Issues ...
Open Graph Description: Problem Statement Currently, Feast has both v1 and v2 document retrieval methods (retrieve_online_documents_v1 and retrieve_online_documents_v2) across different online stores. This creates inconsi...
X Description: Problem Statement Currently, Feast has both v1 and v2 document retrieval methods (retrieve_online_documents_v1 and retrieve_online_documents_v2) across different online stores. This creates inconsi...
Opengraph URL: https://github.com/feast-dev/feast/issues/5537
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Consolidate document retrieval methods: Remove v1 and standardize on v2","articleBody":"## Problem Statement\n\nCurrently, Feast has both v1 and v2 document retrieval methods (`retrieve_online_documents_v1` and `retrieve_online_documents_v2`) across different online stores. This creates inconsistency and maintenance overhead.\n\n**Issues identified:**\n- Different online stores may have different logic between v1 and v2 implementations\n- As noted in [PR #5487](https://github.com/feast-dev/feast/pull/5487#discussion_r2219134015), PostgreSQL online store shows v1 and v2 \"retrieving different dataframes as the logic is completely different for both versions\"\n- v2 was intended to \"incorporate more fields\" but differences beyond that indicate potential bugs\n- Maintaining two versions increases code complexity and testing burden\n\n## Research Required\n\nBefore removing v1, we need to investigate:\n\n### 1. **Cross-Store Analysis**\n- [ ] Audit all online stores that implement both v1 and v2 document retrieval\n- [ ] Document the specific differences in logic between v1 and v2 for each store\n- [ ] Identify which stores have consistent behavior vs. divergent behavior\n\n### 2. **API Compatibility Assessment** \n- [ ] Analyze which version provides more comprehensive/correct results\n- [ ] Compare field coverage between v1 and v2 responses\n- [ ] Evaluate performance characteristics of both versions\n\n### 3. **Usage Analysis**\n- [ ] Identify current usage patterns of v1 vs v2 in the codebase\n- [ ] Check external documentation and examples using these APIs\n- [ ] Assess backward compatibility requirements\n\n### 4. **Store-Specific Investigation**\nFocus on stores mentioned with differences:\n- [ ] **PostgreSQL**: Detailed analysis of why v1/v2 return different dataframes\n- [ ] **Remote store**: Ensure consistency after [PR #5487](https://github.com/feast-dev/feast/pull/5487) implementation\n- [ ] **Other stores**: Milvus, Redis, DynamoDB, etc.\n\n## Proposed Solution\n\nBased on research findings:\n\n### Phase 1: Research \u0026 Documentation\n1. Complete the research items above\n2. Create a comprehensive comparison matrix of v1 vs v2 across all stores\n3. Identify the \"canonical\" version that should be preserved\n\n### Phase 2: Standardization\n1. Ensure v2 implementation is consistent and correct across all stores\n2. Update v2 to include any missing functionality from v1 (if needed)\n3. Add comprehensive tests for v2 across all stores\n\n### Phase 3: Migration \u0026 Removal\n1. Deprecate v1 methods with clear migration guidance\n2. Update all internal usage to v2\n3. Remove v1 implementation after appropriate deprecation period\n\n## Acceptance Criteria\n\n- [ ] All online stores have consistent document retrieval behavior\n- [ ] Single document retrieval API (v2) that works uniformly across stores\n- [ ] Comprehensive test coverage for document retrieval functionality\n- [ ] Migration guide for any external users of v1 API\n- [ ] Updated documentation reflecting the consolidated API\n\n## Context\n\nThis issue stems from the discussion in [PR #5487](https://github.com/feast-dev/feast/pull/5487#discussion_r2219134015) where @franciscojavierarceo noted that v1/v2 differences beyond additional fields indicate bugs, and @jyejare confirmed that different stores have different logic between versions.\n\n**Original comment:**\n\u003e \"v2 vs v1 should be approximately the same where v2 was meant to incorporate more fields. If there is a difference, it's a bug... we should remove v1 and move to v2 for all of the existing usage.\"\n\n## Priority\n\n**Medium-High** - This affects API consistency and maintainability, but doesn't block current functionality.","author":{"url":"https://github.com/jyejare","@type":"Person","name":"jyejare"},"datePublished":"2025-07-24T15:35:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/5537/feast/issues/5537"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:09d7b6e0-34af-4aa3-43a3-6f86172b2ed2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D580:1C9258:87321:BD9E3:696E47B4 |
| html-safe-nonce | c0ab64893e082c3738e1c310d6d0a6b9edcdf13ba7b710b661ae6293e014f058 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJENTgwOjFDOTI1ODo4NzMyMTpCRDlFMzo2OTZFNDdCNCIsInZpc2l0b3JfaWQiOiI4MzUzOTEzOTY0NjIxMzUwODM2IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 2ac0df0bbbe13303bd413b2444861d03bf536c778c448440300a97faf824d1c4 |
| hovercard-subject-tag | issue:3260342008 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/feast-dev/feast/5537/issue_layout |
| twitter:image | https://opengraph.githubassets.com/03a764c54e0e01e9e3cfde3c57712614328613d9e6c992718c01d0d48576dc64/feast-dev/feast/issues/5537 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/03a764c54e0e01e9e3cfde3c57712614328613d9e6c992718c01d0d48576dc64/feast-dev/feast/issues/5537 |
| og:image:alt | Problem Statement Currently, Feast has both v1 and v2 document retrieval methods (retrieve_online_documents_v1 and retrieve_online_documents_v2) across different online stores. This creates inconsi... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | jyejare |
| hostname | github.com |
| expected-hostname | github.com |
| None | 3d96554e55b469c47dbcd31f74dc86278872b170531e84c6ce7f3389673e01d1 |
| turbo-cache-control | no-preview |
| go-import | github.com/feast-dev/feast git https://github.com/feast-dev/feast.git |
| octolytics-dimension-user_id | 57027613 |
| octolytics-dimension-user_login | feast-dev |
| octolytics-dimension-repository_id | 161133770 |
| octolytics-dimension-repository_nwo | feast-dev/feast |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 161133770 |
| octolytics-dimension-repository_network_root_nwo | feast-dev/feast |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | ef576694863a4c791d0a5cc9d2b84384d4414bcd |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width