Description

nquinn408

opened on Feb 5, 2026

Issue body actions

Is your feature request related to a problem? Please describe.
Support Set<Set> or List> as well as Set<List> and List>. Makes sense to support more verbose version of set and list of edge cases.

Describe the solution you'd like
Support set and list

Describe alternatives you've considered
None available as part of definition and proto file

Activity

1. nquinn408

   added

   kind/featureNew feature or requestNew feature or request

   on Feb 5, 2026
2. soooojinlee commented on Feb 23, 2026

   

   soooojinlee

   on Feb 23, 2026

   Contributor

   More actions

   Hi, I'd like to take this on. I'm currently working on UUID/TIME_UUID type support (https://github.com/feastdev/feast/pull/5885) which involved extending types.py, type_map.py, and Value.proto, so I have good context on the type system pipeline.

   Reacted by Nikhil Kathole
3. ntkathole

   assigned

   soooojinlee

   on Feb 23, 2026
4. soooojinlee commented on Mar 13, 2026

   

   soooojinlee

   on Mar 13, 2026

   Contributor

   More actions

   hi, I'm currently working on this and had some questions out of curiosity

   1. use case: Could you share the specific scenario that motivated this request? Knowing what kind of data you're storing as nested collections would help ensure the implementation fits your needs.
   2. depth limit: the examples in issue are 2-level depth limit for now. Is that sufficient, or do you foresee needing deeper nesting?
5. soooojinlee

   added 2 commits that reference this issue on Mar 19, 2026

   feat: Support nested collection types (Array/Set of Array/Set) (feast…

   4ce89b9

   feat: Support nested collection types (Array/Set of Array/Set) (feast…

   0fe7ff6
6. nquinn408 commented on Mar 19, 2026

   

   nquinn408

   on Mar 19, 2026

   ContributorAuthor

   More actions

   hi, I'm currently working on this and had some questions out of curiosity

   1. use case: Could you share the specific scenario that motivated this request? Knowing what kind of data you're storing as nested collections would help ensure the implementation fits your needs.
   2. depth limit: the examples in issue are 2-level depth limit for now. Is that sufficient, or do you foresee needing deeper nesting?

   @soooojinlee , thanks for asking.

   1. I am a platform developer so I am not aware of all of the data science reasons. At the same time, we have MAP (which is a map<string, Value>) and I thought it would be nice to have symmetry and offer LIST (repeated Value) and SET (set<Value>). I know we have xxxLIST and xxxSET for all primitive types so this would just be a catch-all for other List and Set features.
   2. I don't think we should limit at this point since the list and set I proposed above are without bound.

   Reacted by Soojin Lee

   Reacted by Soojin Lee
7. soooojinlee

   added 2 commits that reference this issue on Mar 26, 2026

   feat: Support nested collection types (Array/Set of Array/Set) (feast…

   cd26003

   feat: Support nested collection types (Array/Set of Array/Set) (feast…

   a6e6274
8. ntkathole

   added a commit that references this issue on Apr 2, 2026

   feat: Support nested collection types (Array/Set of Array/Set) (feast…

   5425a92
9. franciscojavierarceo

   added a commit that references this issue on Apr 2, 2026

   feat: Support nested collection types (Array/Set of Array/Set) (#5947) (

   ab61642
10. franciscojavierarceo

    closed this as completedin #6132on Apr 2, 2026
11. franciscojavierarceo

    added 2 commits that reference this issue on Apr 7, 2026

    chore(release): release 0.61.0

    b374396

    chore(release): release 0.62.0

    beaa9a6

Issue actions