[
https://issues.apache.org/jira/browse/LENS-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997953#comment-15997953
]
Hadoop QA commented on LENS-1418:
---------------------------------
Applied patch:
[LENS-1418.04.patch|https://issues.apache.org/jira/secure/attachment/12866573/LENS-1418.04.patch]
and ran command: mvn clean install -fae. Result: Failure. Build Job:
https://builds.apache.org/job/PreCommit-Lens-Build/1290/
> LensClient is not thread safe
> -----------------------------
>
> Key: LENS-1418
> URL: https://issues.apache.org/jira/browse/LENS-1418
> Project: Apache Lens
> Issue Type: Bug
> Components: client
> Reporter: Rajat Khandelwal
> Assignee: Rajat Khandelwal
> Attachments: LENS-1418.01.patch, LENS-1418.03.patch,
> LENS-1418.04.patch
>
>
> Using one lens client to fire two queries in two threads results in
> discrepencies. LensClient has a {{Map<QueryHandle, LensStatement>}} and also
> has a cached instance of {{LensStatement}}. When two threads fire queries,
> both use the same statement object. {{LensStatement}} object in turn caches
> {{LensQuery}} Object. So whichever thread fired query last is the last one to
> set lens query inside statement causing
> {{LensClient.getStatement().getQuery()}} to return that query object for all
> threads.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
