Note that, for maps and lists, there is nothing to set. Maps are purely
containers for other vectors. Lists (you didn't mention whether "repeated" or
"non-repeated") are also containers. Non-repeated lists are containers for
unions, repeated-lists are containers for arrays.
Any setting should be done on the contained vectors. For lists, only the offset
vector is updated.
So, another question is: what is the generated code trying to set?
Thanks,
- Paul
On Wednesday, April 11, 2018, 12:33:52 PM PDT, Padma Penumarthy
<[email protected]> wrote:
Can you explain how aggregation on complex type works (or supposed to work).
Thanks
Padma
> On Apr 11, 2018, at 12:15 PM, Gautam Parai <[email protected]> wrote:
>
> Hi all,
>
>
> I am implementing a new aggregate function which also handles Complex types
> (map and list). However, the codegen barfs with
>
>
> CompileException: Line 104, Column 39: A method named "setSafe" is not
> declared in any enclosing class nor any supertype, nor through a static import
>
>
> It looks like we do not have set()/ setSafe() methods for
> MapVector/ListVector mutators.
>
>
> Should we add these methods to the Mutator interface to ensure all mutators
> implement them? Is these a reason we chose not to do so?
>
>
> Please let me know your thoughts. Thanks!
>
>
> Gautam