rohitsinha54 commented on PR #34363: URL: https://github.com/apache/beam/pull/34363#issuecomment-2764132011
Sorry for the late reply. This is not an urgent change (i.e. not essential for 2.64 release hence not actively following this on my time off). This will only be triggered if the metric result contains bounded trie. So for 2.64 this would not happen unless a customer specifically opt-in to track lineage with boundedtrie or uses boundedtrie metrics (undocumented) in any other way. For the StringSet it happened in that way because lineage emission is enabled by default and was being tracked as StringSet and hence querying /metric for any metric results in StringSet being in result. Yes, we can change it to do something else other than empty values. I will work on that. We will need this as a safeguard before we switch to bounded trie as default metric type for lineage tracking. -- 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: github-unsubscr...@beam.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org