lidavidm commented on PR #779: URL: https://github.com/apache/arrow-java/pull/779#issuecomment-2933011515
> On reflection, simply decoding a dict-encoded vector is not an option because it will leak. I have pushed an update that will reject dict-encoded fields that are not valid Avro enums (check is during schema production). > > I do think automatically decoding dict-encoded fields would be a nicer behaviour. Should we perhaps think about updating the producer pattern to allow for this? E.g. every producer could take an optional index vector, of type BaseIntVector. If that is present, current index is mapped through the index vector which resolves the dictionary index. Would this be ok? So essentially, the "actual" vector would be the dictionary values, and the index vector would contain the "original" encoded vector? I think that sounds OK to me. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
