[ https://issues.apache.org/jira/browse/HIVE-18054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288080#comment-16288080 ]
Andrew Sherman commented on HIVE-18054: --------------------------------------- Test failures are unconnected with this change. So I think this is ready to push [~stakiar] if you agree. > Make Lineage work with concurrent queries on a Session > ------------------------------------------------------- > > Key: HIVE-18054 > URL: https://issues.apache.org/jira/browse/HIVE-18054 > Project: Hive > Issue Type: Bug > Reporter: Andrew Sherman > Assignee: Andrew Sherman > Attachments: HIVE-18054.1.patch, HIVE-18054.10.patch, > HIVE-18054.11.patch, HIVE-18054.12.patch, HIVE-18054.13.patch, > HIVE-18054.2.patch, HIVE-18054.3.patch, HIVE-18054.4.patch, > HIVE-18054.5.patch, HIVE-18054.6.patch, HIVE-18054.7.patch, > HIVE-18054.8.patch, HIVE-18054.9.patch > > > A Hive Session can contain multiple concurrent sql Operations. > Lineage is currently tracked in SessionState and is cleared when a query > completes. This results in Lineage for other running queries being lost. > To fix this, move LineageState from SessionState to QueryState. -- This message was sent by Atlassian JIRA (v6.4.14#64029)