Re: Review Request 45286: AlarmService for the Scheduler

ll/Should the schedule service retrigger this schedule on startup? - Puneet Gupta On March 24, 2016, 2:09 p.m., Ajay Yadava wrote: > > --- > This is an automatically generated e-mail. To reply, visi

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

rows processed in (9) seconds. Thanks, Puneet Gupta

Re: Review Request 45273: LENS-993 : Fix thread pool creations on server

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45273/#review125236 --- Ship it! Ship It! - Puneet Gupta On March 24, 2016, 6:36

Re: Review Request 45273: LENS-993 : Fix thread pool creations on server

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45273/#review125233 --- +1. - Puneet Gupta On March 24, 2016, 6:36 a.m., Amareshwari

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

t: https://reviews.apache.org/r/44171/#review125194 ------- On March 22, 2016, 1:52 a.m., Puneet Gupta wrote: > > --- > This is an automatically generated e

Re: Review Request 45100: LENS-819 Timeline of the fact returned should have structure instead of String

> On March 22, 2016, 4:41 a.m., Puneet Gupta wrote: > > lens-api/src/main/java/org/apache/lens/api/TimeLines.java, line 71 > > <https://reviews.apache.org/r/45100/diff/1/?file=1308326#file1308326line71> > > > > All implementations of PartitionTime

Re: Review Request 45207: LENS-893 : Add exponential backoff for next update of status update, incase of failures from driver

> should we make the arguments statusUpdateRetryMaxDelay and statusUpdateExponentialWaitFactor as class memebers instead in QueryContext and ExponentialBackOffRetryHandler ? - Puneet Gupta On March 23, 2016, 10:28 a.m., Amare

Re: Review Request 45100: LENS-819 Timeline of the fact returned should have structure instead of String

> On March 22, 2016, 4:41 a.m., Puneet Gupta wrote: > > lens-api/src/main/java/org/apache/lens/api/TimeLines.java, line 71 > > <https://reviews.apache.org/r/45100/diff/1/?file=1308326#file1308326line71> > > > > All implementations of PartitionTime

Re: Review Request 45028: LENS-317: Server side calls for updating database jars

exception loggeed has the exeception class name already lens-server/src/main/java/org/apache/lens/server/metastore/CubeMetastoreServiceImpl.java (line 929) <https://reviews.apache.org/r/45028/#comment187773> This can be the first statement in finally, just to make sure its always e

Re: [VOTE] Release of Apache Lens 2.5.0-beta

+1 for releasing this candidate + was able to download source and binary + was able to start lens server and run all the examples successfully (Successful queries 148 out of 148queries) + tested lens-cli + checked license file Thanks, Puneet Gupta On Tue, Mar 22, 2016 at 8:10 PM, Raju

Re: Review Request 45100: LENS-819 Timeline of the fact returned should have structure instead of String

gt; Should we have a new line between fields . Not sure of how it ll look in CLI though. If possible pls share a snapshot from cli. - Puneet Gupta On March 21, 2016, 12:15 p.m., Ajay Yadava wrote: > > --- > This is a

Re: Review Request 45099: LENS-991: Seeing multiple close calls and failures of connection after LENS-853

mmands/BaseLensCommand.java (line 81) <https://reviews.apache.org/r/45099/#comment187354> Do u think we need to synchronoize ? From what I know synchronization will not be required since commands can not be created parallay on cli. - Puneet Gupta On March 21, 2016, 11:4

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

compare objects always? Why do we need to compare > > `toString`s first? > > Puneet Gupta wrote: > In some cases objects dont have overridden equals like QueryStatus. In > such cases the comparison fails. Wanted to make use of toString() in that > case, which sho

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

39.csv 7 rows processed in (9) seconds. Thanks, Puneet Gupta

[jira] [Commented] (LENS-819) Timeline of the fact returned should have structure instead of String

[ https://issues.apache.org/jira/browse/LENS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203644#comment-15203644 ] Puneet Gupta commented on LENS-819: --- Can you post the review board URL on jira. Not able to find

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

ext patch. > On March 19, 2016, 2:54 p.m., Rajat Khandelwal wrote: > > lens-cli/src/test/java/org/apache/lens/cli/TestLensQueryCommands.java, line > > 552 > > <https://reviews.apache.org/r/44171/diff/5/?file=1300904#file1300904line552> > > > > casting not needed. Will remove. - Puneet ---

[jira] [Commented] (LENS-990) Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries

[ https://issues.apache.org/jira/browse/LENS-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203116#comment-15203116 ] Puneet Gupta commented on LENS-990: --- Not seeing this failure in local build. Should i re run per-commit

[jira] [Commented] (LENS-990) Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries

[ https://issues.apache.org/jira/browse/LENS-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201204#comment-15201204 ] Puneet Gupta commented on LENS-990: --- https://reviews.apache.org/r/45021 > Seeing fecthresult fail

Re: Review Request 44436: LENS-919: Persist Query Priority in Lens DB

- in org.apache.lens.server.query.TestQueryService Results : Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Thanks, Puneet Gupta

[jira] [Updated] (LENS-919) Persist Query Priority in Lens DB

[ https://issues.apache.org/jira/browse/LENS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-919: -- Status: In Progress (was: Patch Available) > Persist Query Priority in Lens

[jira] [Updated] (LENS-919) Persist Query Priority in Lens DB

[ https://issues.apache.org/jira/browse/LENS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-919: -- Attachment: lens-919.03.patch > Persist Query Priority in Lens

[jira] [Updated] (LENS-919) Persist Query Priority in Lens DB

[ https://issues.apache.org/jira/browse/LENS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-919: -- Status: Patch Available (was: In Progress) > Persist Query Priority in Lens

[jira] [Commented] (LENS-990) Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries

[ https://issues.apache.org/jira/browse/LENS-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201192#comment-15201192 ] Puneet Gupta commented on LENS-990: --- Taking patch from reviewboard and attaching > Seeing fecthres

Review Request 45021: LENS-990: Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries

] Thanks, Puneet Gupta

[jira] [Assigned] (LENS-990) Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries

[ https://issues.apache.org/jira/browse/LENS-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta reassigned LENS-990: - Assignee: Puneet Gupta > Seeing fecthresult failing with ' Expected state FINISHED, but fo

[jira] [Commented] (LENS-919) Persist Query Priority in Lens DB

[ https://issues.apache.org/jira/browse/LENS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198745#comment-15198745 ] Puneet Gupta commented on LENS-919: --- Taking patch from reviewboard and attaching > Persist Query Prior

[jira] [Created] (LENS-990) Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries

Puneet Gupta created LENS-990: - Summary: Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries Key: LENS-990 URL: https://issues.apache.org/jira/browse/LENS-990

Re: Review Request 45021: LENS-990: Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries

This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45021/#review124163 --- On March 18, 2016, 7:17 a.m., Puneet Gupta wrote: > > -

[jira] [Commented] (LENS-990) Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries

[ https://issues.apache.org/jira/browse/LENS-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201038#comment-15201038 ] Puneet Gupta commented on LENS-990: --- Once a Query is candidate for Purge , we create an instance

Re: Review Request 45028: LENS-317: Server side calls for updating database jars

SON,TEXT_PLAIN lens-server/src/main/java/org/apache/lens/server/metastore/MetastoreResource.java (line 1734) <https://reviews.apache.org/r/45028/#comment186623> Needs to be logged via logger Partial review .. - Puneet Gu

[jira] [Updated] (LENS-919) Persist Query Priority in Lens DB

[ https://issues.apache.org/jira/browse/LENS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-919: -- Status: Patch Available (was: Reopened) > Persist Query Priority in Lens

[jira] [Updated] (LENS-990) Seeing fecthresult failing with ' Expected state FINISHED, but found ERROR' for failed hive queries

[ https://issues.apache.org/jira/browse/LENS-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-990: -- Status: Patch Available (was: Open) > Seeing fecthresult failing with ' Expected state FINIS

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

6cf] sample_dim.namesample_dim2.name Results of query stored at : file:/tmp/lensreports/1eb498e5-13c5-454f-a093-0fc08171d539.csv 7 rows processed in (9) seconds. Thanks, Puneet Gupta

[jira] [Updated] (LENS-989) Support HBase Storage for Lens

[ https://issues.apache.org/jira/browse/LENS-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-989: -- Labels: gsoc2016 java (was: gsoc2016) > Support HBase Storage for L

[jira] [Created] (LENS-989) Support HBase Storage for Lens

Puneet Gupta created LENS-989: - Summary: Support HBase Storage for Lens Key: LENS-989 URL: https://issues.apache.org/jira/browse/LENS-989 Project: Apache Lens Issue Type: New Feature

Re: Review Request 44612: LENS-975 : Add cube-segmentation specification

on candidate cubes and their facts ? - Puneet Gupta On March 10, 2016, 8:33 a.m., Sushil Mohanty wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://re

Re: Review Request 44436: LENS-919: Persist Query Priority in Lens DB

-- Running org.apache.lens.server.query.TestQueryService Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 63.063 sec - in org.apache.lens.server.query.TestQueryService Results : Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Thanks, Puneet Gupta

Re: Review Request 44436: LENS-919: Persist Query Priority in Lens DB

-- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44436/#review123393 --- On March 7, 2016, 4:30 a.m., Puneet Gupta wrote: > > ---

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

tring getUserQuery() { return getQuery().getUserQuery(); } This will be more intutive for adding new code. - Puneet ------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44171/#revie

[jira] [Updated] (LENS-978) Default value of "lens.client.query.poll.interval" is very small

[ https://issues.apache.org/jira/browse/LENS-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-978: -- Status: Patch Available (was: In Progress) > Default value of "lens.client.query.poll.interval&

[jira] [Updated] (LENS-978) Default value of "lens.client.query.poll.interval" is very small

[ https://issues.apache.org/jira/browse/LENS-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-978: -- Attachment: lens-978.v1.patch Taking patch form review board and attaching > Default va

[jira] [Updated] (LENS-919) Persist Query Priority in Lens DB

[ https://issues.apache.org/jira/browse/LENS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-919: -- Status: Patch Available (was: In Progress) > Persist Query Priority in Lens

[jira] [Updated] (LENS-919) Persist Query Priority in Lens DB

[ https://issues.apache.org/jira/browse/LENS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-919: -- Attachment: lens-919.patch Taking patch form review board and attaching > Persist Query Priority in L

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

ose interfaces will return LensQuery type objects. ProxyLensQuery will not be exposed directly. - Puneet --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44171/#review122257 --

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

e:/tmp/lensreports/1eb498e5-13c5-454f-a093-0fc08171d539.csv 7 rows processed in (9) seconds. Thanks, Puneet Gupta

[jira] [Created] (LENS-984) Response type of prepared query execution REST end point /queryapi/preparedqueries/{prepareHandle} should be wrapped in LensAPIResult

Puneet Gupta created LENS-984: - Summary: Response type of prepared query execution REST end point /queryapi/preparedqueries/{prepareHandle} should be wrapped in LensAPIResult Key: LENS-984 URL: https

Re: Review Request 44438: LENS-978: Default value of "lens.client.query.poll.interval" is very small

ttps://reviews.apache.org/r/44438/#review122284 --- On March 7, 2016, 6 a.m., Puneet Gupta wrote: > > --- > This is an automatically generated e-mail. To reply, v

[jira] [Commented] (LENS-978) Default value of "lens.client.query.poll.interval" is very small

[ https://issues.apache.org/jira/browse/LENS-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15182629#comment-15182629 ] Puneet Gupta commented on LENS-978: --- created https://reviews.apache.org/r/44438/diff/ > Default va

Review Request 44438: LENS-978: Default value of "lens.client.query.poll.interval" is very small

--- Thanks, Puneet Gupta

[jira] [Work started] (LENS-978) Default value of "lens.client.query.poll.interval" is very small

[ https://issues.apache.org/jira/browse/LENS-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-978 started by Puneet Gupta. - > Default value of "lens.client.query.poll.interval"

Re: Review Request 44436: LENS-919: Persist Query Priority in Lens DB

org.apache.lens.server.query.TestQueryService Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 63.063 sec - in org.apache.lens.server.query.TestQueryService Results : Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Thanks, Puneet Gupta

Review Request 44436: LENS-919: Persist Query Priority in Lens DB

/ Testing --- Thanks, Puneet Gupta

[jira] [Commented] (LENS-919) Persist Query Priority in Lens DB

[ https://issues.apache.org/jira/browse/LENS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15182567#comment-15182567 ] Puneet Gupta commented on LENS-919: --- Created https://reviews.apache.org/r/44436/ > Persist Query Prior

[jira] [Work started] (LENS-919) Persist Query Priority in Lens DB

[ https://issues.apache.org/jira/browse/LENS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-919 started by Puneet Gupta. - > Persist Query Priority in Lens

Re: Review Request 44415: LENS-983 : Make default response type as XML on session, metastore and query resources

ource.java: @Produces({MediaType.APPLICATION_JSON, MediaType.APPLICATION_XML, MediaType.TEXT_PLAIN}) - Puneet Gupta On March 5, 2016, 4:12 a.m., Amareshwari Sriramadasu wrote: > > --- > This is an automatically generated e-mail. To re

[jira] [Commented] (LENS-983) All Lens REST end points should support MediaType.APPLICATION_XML as default MIME Type

[ https://issues.apache.org/jira/browse/LENS-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15180486#comment-15180486 ] Puneet Gupta commented on LENS-983: --- {noformat} @Produces({MediaType.APPLICATION_JSON

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

r()=e28bb36f-7243-4568-8b2f-3dfbbf34e6cf] sample_dim.namesample_dim2.name Results of query stored at : file:/tmp/lensreports/1eb498e5-13c5-454f-a093-0fc08171d539.csv 7 rows processed in (9) seconds. Thanks, Puneet Gupta

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

https://reviews.apache.org/r/44171/#review122044 ------- On Feb. 29, 2016, 2:19 p.m., Puneet Gupta wrote: > > --- > This is an automatically generated e-m

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

eviews.apache.org/r/44171/#review121418 --- On Feb. 29, 2016, 2:19 p.m., Puneet Gupta wrote: > > --- > This is an automatically generated e-mail. To re

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

> On March 1, 2016, 2:07 a.m., Puneet Gupta wrote: > > lens-client/src/main/java/org/apache/lens/client/LensStatement.java, line > > 360 > > <https://reviews.apache.org/r/44171/diff/1/?file=1273933#file1273933line360> > > > > Should we try to prevent t

[jira] [Updated] (LENS-964) Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing

[ https://issues.apache.org/jira/browse/LENS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-964: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Lens-cli test c

[jira] [Commented] (LENS-964) Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing

[ https://issues.apache.org/jira/browse/LENS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175408#comment-15175408 ] Puneet Gupta commented on LENS-964: --- Committed myself. > Lens-cli test c

[jira] [Created] (LENS-981) Add Memory gatekeepers for InMemoryResultSet to prevent any OOM on lens server

Puneet Gupta created LENS-981: - Summary: Add Memory gatekeepers for InMemoryResultSet to prevent any OOM on lens server Key: LENS-981 URL: https://issues.apache.org/jira/browse/LENS-981 Project: Apache

Re: Review Request 43929: Fixed Test cases for TestLensQueryCommands LENS-964

--- Running org.apache.lens.cli.TestLensQueryCommands Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 230.846 sec - in org.apache.lens.cli.TestLensQueryCommands Results : Tests run: 14, Failures: 0, Errors: 0, Skipped: 0 Thanks, Puneet Gupta

[jira] [Updated] (LENS-964) Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing

[ https://issues.apache.org/jira/browse/LENS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-964: -- Status: Patch Available (was: In Progress) > Lens-cli test case TestLensQueryCommands.executeSyncQu

[jira] [Updated] (LENS-964) Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing

[ https://issues.apache.org/jira/browse/LENS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-964: -- Attachment: lens-964.v2.patch Attaching patch form review board > Lens-cli test c

Re: Review Request 43929: Fixed Test cases for TestLensQueryCommands LENS-964

e still have this back and assert error for fetching again? > > Puneet Gupta wrote: > Second fetch is not resulting in error since the query takes some time to > purge. Its returning blank result with zero rows since all rows have been > read already (and we are not seeking to start o

Re: Review Request 43929: Fixed Test cases for TestLensQueryCommands LENS-964

me elapsed: 230.846 sec - in org.apache.lens.cli.TestLensQueryCommands Results : Tests run: 14, Failures: 0, Errors: 0, Skipped: 0 Thanks, Puneet Gupta

[jira] [Created] (LENS-979) A client should not be able to fetch InMemory Results more than once

Puneet Gupta created LENS-979: - Summary: A client should not be able to fetch InMemory Results more than once Key: LENS-979 URL: https://issues.apache.org/jira/browse/LENS-979 Project: Apache Lens

[jira] [Commented] (LENS-915) Update CLI to show streaming results

[ https://issues.apache.org/jira/browse/LENS-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173104#comment-15173104 ] Puneet Gupta commented on LENS-915: --- https://reviews.apache.org/r/44171/ > Update CLI to show stream

Re: Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

/LensStatement.java (line 359) <https://reviews.apache.org/r/44171/#comment183058> Should we try to prevent this extra call ? It can introduce delay in streaming for users who are relying on LensClient/LensStatement. - Puneet Gupta On Feb. 29, 2016, 2:19 p.m., Puneet Gupta

Review Request 44171: Lens-915 : query execute (non async option) should use EXECUTE_WITH_TIMEOUT option instead of EXECUTE followed by status polling

r()=e28bb36f-7243-4568-8b2f-3dfbbf34e6cf] sample_dim.namesample_dim2.name Results of query stored at : file:/tmp/lensreports/1eb498e5-13c5-454f-a093-0fc08171d539.csv 7 rows processed in (9) seconds. Thanks, Puneet Gupta

Re: [ANNOUNCE] New Apache Lens committer : Puneet Gupta

Thank you guys :-) On Fri, Feb 26, 2016 at 9:46 PM, Arshad Matin wrote: > Congrats Puneet :) > > On Fri, Feb 26, 2016 at 9:36 PM, Ankeet Maini > wrote: > >> Congrats! >> >> On Fri, Feb 26, 2016, 5:10 PM Deepak Kumar Barr (Tech_BLR) < >>

[jira] [Created] (LENS-978) Default value of "lens.client.query.poll.interval" is very small

Puneet Gupta created LENS-978: - Summary: Default value of "lens.client.query.poll.interval" is very small Key: LENS-978 URL: https://issues.apache.org/jira/browse/LENS-978 Project: A

[jira] [Comment Edited] (LENS-973) On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled

[ https://issues.apache.org/jira/browse/LENS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15167020#comment-15167020 ] Puneet Gupta edited comment on LENS-973 at 2/26/16 7:31 AM: This happens when 1

[jira] [Comment Edited] (LENS-973) On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled

[ https://issues.apache.org/jira/browse/LENS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15167020#comment-15167020 ] Puneet Gupta edited comment on LENS-973 at 2/26/16 7:30 AM: This happens when 1

[jira] [Comment Edited] (LENS-973) On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled

[ https://issues.apache.org/jira/browse/LENS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15167020#comment-15167020 ] Puneet Gupta edited comment on LENS-973 at 2/26/16 7:31 AM: This happens when 1

[jira] [Comment Edited] (LENS-973) On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled

[ https://issues.apache.org/jira/browse/LENS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15167020#comment-15167020 ] Puneet Gupta edited comment on LENS-973 at 2/25/16 10:06 AM: - This happens when

[jira] [Assigned] (LENS-973) On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled

[ https://issues.apache.org/jira/browse/LENS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta reassigned LENS-973: - Assignee: Puneet Gupta > On Server restart not able to launch new queries on hive if qu

[jira] [Commented] (LENS-973) On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled

[ https://issues.apache.org/jira/browse/LENS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15167020#comment-15167020 ] Puneet Gupta commented on LENS-973: --- This happens when 1. At least one query is running on hive driver 2

[jira] [Created] (LENS-973) On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled

Puneet Gupta created LENS-973: - Summary: On Server restart not able to launch new queries on hive if queue constraint driver.max.concurrent.launched.queries.per.queue is enabled Key: LENS-973 URL: https

[jira] [Commented] (LENS-972) Seeing XMLMarshalException while unmarshalling inMemoryQueryResult from json

[ https://issues.apache.org/jira/browse/LENS-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15166755#comment-15166755 ] Puneet Gupta commented on LENS-972: --- Was trying execute_with_timeout options when I encountered

[jira] [Updated] (LENS-972) Seeing XMLMarshalException while unmarshalling inMemoryQueryResult from json

[ https://issues.apache.org/jira/browse/LENS-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-972: -- Summary: Seeing XMLMarshalException while unmarshalling inMemoryQueryResult from json (was: Seeing

[jira] [Created] (LENS-972) Seeing XMLMarshalException while unmarshalling inMemoryQueryResult

Puneet Gupta created LENS-972: - Summary: Seeing XMLMarshalException while unmarshalling inMemoryQueryResult Key: LENS-972 URL: https://issues.apache.org/jira/browse/LENS-972 Project: Apache Lens

Re: Review Request 39576: LENS-833 : Limit number of open sessions per user on session service

Status or LensHttpStatus. - Puneet Gupta On Feb. 23, 2016, 2:38 p.m., Raju Bairishetti wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.

[jira] [Work started] (LENS-915) Update CLI to show streaming results

[ https://issues.apache.org/jira/browse/LENS-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-915 started by Puneet Gupta. - > Update CLI to show streaming resu

[jira] [Work started] (LENS-964) Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing

[ https://issues.apache.org/jira/browse/LENS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-964 started by Puneet Gupta. - > Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skip

Re: Review Request 43929: Fixed Test cases for TestLensQueryCommands LENS-964

ated e-mail. To reply, visit: https://reviews.apache.org/r/43929/#review120457 ------- On Feb. 24, 2016, 3:23 a.m., Puneet Gupta wrote: > > --- > This is a

[jira] [Commented] (LENS-964) Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing

[ https://issues.apache.org/jira/browse/LENS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160193#comment-15160193 ] Puneet Gupta commented on LENS-964: --- https://reviews.apache.org/r/43929/ > Lens-cli test c

Re: Review Request 39576: LENS-833 : Limit number of open sessions per user on session service

e code of Response.Status here. - Puneet Gupta On Jan. 20, 2016, 3:11 p.m., Raju Bairishetti wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.

[jira] [Closed] (LENS-875) Move TestQueryConstraints to create two instances of HiveDriver instead of creating instances of its two dummy subclasses

[ https://issues.apache.org/jira/browse/LENS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta closed LENS-875. - Fixed with Lens-123 > Move TestQueryConstraints to create two instances of HiveDriver instead of > cr

[jira] [Commented] (LENS-964) Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing

[ https://issues.apache.org/jira/browse/LENS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156524#comment-15156524 ] Puneet Gupta commented on LENS-964: --- 7 test cases for TestLensQueryCommands getting skipped but build

[jira] [Updated] (LENS-964) Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing

[ https://issues.apache.org/jira/browse/LENS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-964: -- Description: mvn clean test -Dtest=org.apache.lens.cli.TestLensQueryCommands#executeSyncQuery

[jira] [Created] (LENS-964) Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing

Puneet Gupta created LENS-964: - Summary: Lens-cli test case TestLensQueryCommands.executeSyncQuery() getting skipped but build is passing Key: LENS-964 URL: https://issues.apache.org/jira/browse/LENS-964

Re: Review Request 43600: LENS-960: getting string from AST should give flat string wherever possible

de lens-cube module also. Any chnages to test cases outside of lens-cube ? - Puneet Gupta On Feb. 16, 2016, 2:30 p.m., Rajat Khandelwal wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://re

[jira] [Updated] (LENS-931) Result path not updated in query details when server persistence is enabled

[ https://issues.apache.org/jira/browse/LENS-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-931: -- Status: Patch Available (was: In Progress) > Result path not updated in query details when ser

[jira] [Updated] (LENS-931) Result path not updated in query details when server persistence is enabled

[ https://issues.apache.org/jira/browse/LENS-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-931: -- Attachment: lens-931.v1.patch Attaching patch from review board > Result path not updated in qu

Re: Review Request 43320: LENS-931 Test case

--- Running org.apache.lens.server.query.TestQueryService Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 130.817 sec - in org.apache.lens.server.query.TestQueryService Results : Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Thanks, Puneet Gupta

[jira] [Updated] (LENS-931) Result path not updated in query details

[ https://issues.apache.org/jira/browse/LENS-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-931: -- Fix Version/s: 2.6 > Result path not updated in query deta

[jira] [Work started] (LENS-931) Result path not updated in query details

[ https://issues.apache.org/jira/browse/LENS-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-931 started by Puneet Gupta. - > Result path not updated in query deta

<    3   4   5   6   7   8   9   10   >