[jira] [Commented] (LENS-893) Query Service should not mark queries failed in case driver is not responding in a timely manner

[ https://issues.apache.org/jira/browse/LENS-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215502#comment-15215502 ] Hadoop QA commented on LENS-893: Applied patch: [LENS-893.4.patch|https://issues.apache.org

[jira] [Commented] (LENS-893) Query Service should not mark queries failed in case driver is not responding in a timely manner

[ https://issues.apache.org/jira/browse/LENS-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215501#comment-15215501 ] Hadoop QA commented on LENS-893: Applied patch: [LENS-893.4.patch|https://issues.apache.org

[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&focusedCommentId=15215473#comment-15215473 ] Hadoop QA commented on LENS-915: Applied patch: [LENS-915.08.patch|https://issues.apache.or

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

> On March 29, 2016, 5:07 a.m., Rajat Khandelwal wrote: > > lens-server-api/src/main/java/org/apache/lens/server/api/common/FailureContext.java, > > line 27 > > > > > > Should the name be more revealing of the fact t

[jira] [Resolved] (LENS-483) Consistent way of receiving request data in REST APIs

[ https://issues.apache.org/jira/browse/LENS-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu resolved LENS-483. -- Resolution: Duplicate Fix Version/s: (was: 2.6) > Consistent way of rec

[jira] [Reopened] (LENS-483) Consistent way of receiving request data in REST APIs

[ https://issues.apache.org/jira/browse/LENS-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu reopened LENS-483: -- > Consistent way of receiving request data in REST APIs >

[jira] [Updated] (LENS-483) Consistent way of receiving request data in REST APIs

[ https://issues.apache.org/jira/browse/LENS-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu updated LENS-483: - Status: Reopened (was: Reopened) > Consistent way of receiving request data in REST

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

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45207/#review125817 --- lens-server-api/src/main/java/org/apache/lens/server/api/common/E

[jira] [Commented] (LENS-483) Consistent way of receiving request data in REST APIs

[ https://issues.apache.org/jira/browse/LENS-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215436#comment-15215436 ] Amareshwari Sriramadasu commented on LENS-483: -- [~prongs], The api in QueryServ

[jira] [Commented] (LENS-42) Get all queries to return all query details instead of handles

[ https://issues.apache.org/jira/browse/LENS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215428#comment-15215428 ] Rajat Khandelwal commented on LENS-42: -- I'm only concerned about driver query, which is

Re: Review Request 45382: LENS-995 : QueryContextPriorityComparator should compare the priorities instead of cost

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45382/#review125812 --- lens-server/src/main/java/org/apache/lens/server/query/QueryConte

[jira] [Commented] (LENS-42) Get all queries to return all query details instead of handles

[ https://issues.apache.org/jira/browse/LENS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215419#comment-15215419 ] Ajay Yadava commented on LENS-42: - I think giving only handles is not very helpful and doesn'

[jira] [Updated] (LENS-893) Query Service should not mark queries failed in case driver is not responding in a timely manner

[ https://issues.apache.org/jira/browse/LENS-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu updated LENS-893: - Attachment: LENS-893.4.patch > Query Service should not mark queries failed in case

[jira] [Updated] (LENS-893) Query Service should not mark queries failed in case driver is not responding in a timely manner

[ https://issues.apache.org/jira/browse/LENS-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu updated LENS-893: - Status: Patch Available (was: In Progress) Review at https://reviews.apache.org/r/4

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

> On March 28, 2016, 1:39 p.m., Puneet Gupta wrote: > > UpdateStatus() is called from getUpdatedQueryContext() also. Do we need to > > fail fast in some specific cases without retrying? > > I am not sure. Most callers of getUpdatedQueryContext look fine with > > retries. Please check once from

[jira] [Updated] (LENS-42) Get all queries to return all query details instead of handles

[ https://issues.apache.org/jira/browse/LENS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-42: - Status: Open (was: Patch Available) > Get all queries to return all query details instead of handles

[jira] [Commented] (LENS-42) Get all queries to return all query details instead of handles

[ https://issues.apache.org/jira/browse/LENS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215407#comment-15215407 ] Rajat Khandelwal commented on LENS-42: -- I don't think we should give all details. Those

[jira] [Commented] (LENS-483) Consistent way of receiving request data in REST APIs

[ https://issues.apache.org/jira/browse/LENS-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215400#comment-15215400 ] Rajat Khandelwal commented on LENS-483: --- There's still one place where sessionid is ta

[jira] [Commented] (LENS-918) Query Priority is not getting logged in query logs

[ https://issues.apache.org/jira/browse/LENS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215295#comment-15215295 ] Puneet Gupta commented on LENS-918: --- I think the problem earlier was that the log segregat

Re: Review Request 45382: LENS-995 : QueryContextPriorityComparator should compare the priorities instead of cost

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45382/#review125795 --- lens-server/src/main/java/org/apache/lens/server/query/QueryConte

[jira] [Updated] (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 ] Puneet Gupta updated LENS-915: -- Status: Open (was: Patch Available) > Update CLI to show streaming results >

[jira] [Updated] (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 ] Puneet Gupta updated LENS-915: -- Status: Patch Available (was: Open) > Update CLI to show streaming results >

[jira] [Assigned] (LENS-27) Query caching layer in lens server

[ https://issues.apache.org/jira/browse/LENS-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajitha R reassigned LENS-27: - Assignee: Rajitha R > Query caching layer in lens server > -- > >

Re: Review Request 45382: LENS-995 : QueryContextPriorityComparator should compare the priorities instead of cost

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45382/#review125694 --- Ship it! +1 LGTM - Ajay Yadava On March 28, 2016, 5:03 p.m.,

Re: Review Request 45382: LENS-995 : QueryContextPriorityComparator should compare the priorities instead of cost

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45382/ --- (Updated March 28, 2016, 5:03 p.m.) Review request for lens. Changes ---

[jira] [Commented] (LENS-42) Get all queries to return all query details instead of handles

[ https://issues.apache.org/jira/browse/LENS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214309#comment-15214309 ] Hadoop QA commented on LENS-42: --- Applied patch: [LENS-42.patch|https://issues.apache.org/jira/

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

[ https://issues.apache.org/jira/browse/LENS-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214310#comment-15214310 ] Hadoop QA commented on LENS-984: Applied patch: [LENS-984.patch|https://issues.apache.org/j

[jira] [Commented] (LENS-165) Improve LensJerseyTest

[ https://issues.apache.org/jira/browse/LENS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214283#comment-15214283 ] Hadoop QA commented on LENS-165: Applied patch: [LENS-165.patch|https://issues.apache.org/j

Review Request 45382: LENS-995 : QueryContextPriorityComparator should compare the priorities instead of cost

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45382/ --- Review request for lens. Bugs: LENS-995 https://issues.apache.org/jira/brow

[jira] [Commented] (LENS-42) Get all queries to return all query details instead of handles

[ https://issues.apache.org/jira/browse/LENS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214261#comment-15214261 ] Ajay Yadava commented on LENS-42: - Discussed with [~akshaygoyal], assigned to myself. > Get

[jira] [Assigned] (LENS-42) Get all queries to return all query details instead of handles

[ https://issues.apache.org/jira/browse/LENS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava reassigned LENS-42: --- Assignee: Ajay Yadava (was: Akshay Goyal) > Get all queries to return all query details instead of hand

[jira] [Updated] (LENS-42) Get all queries to return all query details instead of handles

[ https://issues.apache.org/jira/browse/LENS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated LENS-42: Status: Patch Available (was: Open) > Get all queries to return all query details instead of handles > ---

[jira] [Updated] (LENS-42) Get all queries to return all query details instead of handles

[ https://issues.apache.org/jira/browse/LENS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated LENS-42: Attachment: LENS-42.patch > Get all queries to return all query details instead of handles > --

[jira] [Resolved] (LENS-483) Consistent way of receiving request data in REST APIs

[ https://issues.apache.org/jira/browse/LENS-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava resolved LENS-483. -- Resolution: Fixed Assignee: Amareshwari Sriramadasu This issues seems to have been already fixed by

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

[ https://issues.apache.org/jira/browse/LENS-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated LENS-984: - Status: Patch Available (was: Open) > Response type of prepared query execution REST end point > /queryapi

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

[ https://issues.apache.org/jira/browse/LENS-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated LENS-984: - Attachment: LENS-984.patch Attaching patch here to test the patch, will put the reviewboard request once th

[jira] [Commented] (LENS-918) Query Priority is not getting logged in query logs

[ https://issues.apache.org/jira/browse/LENS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214238#comment-15214238 ] Hadoop QA commented on LENS-918: Applied patch: [LENS-918.patch|https://issues.apache.org/j

[jira] [Updated] (LENS-165) Improve LensJerseyTest

[ https://issues.apache.org/jira/browse/LENS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated LENS-165: - Status: Patch Available (was: Open) > Improve LensJerseyTest > -- > > K

[jira] [Updated] (LENS-165) Improve LensJerseyTest

[ https://issues.apache.org/jira/browse/LENS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated LENS-165: - Attachment: LENS-165.patch This patch addresses issues #1. Attaching file here to test the patch. Will put

[jira] [Assigned] (LENS-165) Improve LensJerseyTest

[ https://issues.apache.org/jira/browse/LENS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava reassigned LENS-165: Assignee: Ajay Yadava > Improve LensJerseyTest > -- > > Key: LENS

[jira] [Commented] (LENS-918) Query Priority is not getting logged in query logs

[ https://issues.apache.org/jira/browse/LENS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214218#comment-15214218 ] Rajat Khandelwal commented on LENS-918: --- Is it required? Seeing as the log handle is a

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

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45207/#review125631 --- Ship it! UpdateStatus() is called from getUpdatedQueryContext()

[jira] [Updated] (LENS-918) Query Priority is not getting logged in query logs

[ https://issues.apache.org/jira/browse/LENS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated LENS-918: - Attachment: LENS-918.patch Trivial patch, so assuming review board request is not required. > Query Priorit

[jira] [Updated] (LENS-918) Query Priority is not getting logged in query logs

[ https://issues.apache.org/jira/browse/LENS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated LENS-918: - Status: Patch Available (was: Open) > Query Priority is not getting logged in query logs >

[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&focusedCommentId=15214174#comment-15214174 ] Hadoop QA commented on LENS-915: Applied patch: [LENS-915.08.patch|https://issues.apache.or

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

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45207/ --- (Updated March 28, 2016, 12:40 p.m.) Review request for lens. Changes ---

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

> On March 28, 2016, 10:41 a.m., Puneet Gupta wrote: > > lens-server-api/src/main/java/org/apache/lens/server/api/query/QueryContext.java, > > line 389 > > > > > > Should we also log the execption as Warning incase

[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&focusedCommentId=15214137#comment-15214137 ] Puneet Gupta commented on LENS-915: --- Taking patch from reviewboard and attaching > Update

[jira] [Updated] (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 ] Puneet Gupta updated LENS-915: -- Attachment: LENS-915.08.patch > Update CLI to show streaming results > ---

[jira] [Updated] (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 ] Puneet Gupta updated LENS-915: -- Status: Patch Available (was: In Progress) > Update CLI to show streaming results > -

[jira] [Commented] (LENS-975) Add cube-segmentation specification

[ https://issues.apache.org/jira/browse/LENS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214134#comment-15214134 ] Hudson commented on LENS-975: - SUCCESS: Integrated in Lens-Commit-Java8 #125 (See [https://buil

[jira] [Commented] (LENS-982) lens-ml-lib build timing out on some environments

[ https://issues.apache.org/jira/browse/LENS-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214135#comment-15214135 ] Hudson commented on LENS-982: - SUCCESS: Integrated in Lens-Commit-Java8 #125 (See [https://buil

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

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44171/ --- (Updated March 28, 2016, 12:08 p.m.) Review request for lens. Changes ---

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

Correction - -- Vote has passed with 3 [+1] binding votes and no [0] or [-1] votes. +1 votes: Raju Bairishetti Amareshwari SriRamadasu Jean-Baptiste Onofré Puneet Gupta (non-binding) Sushil Mohanty (non-bindi

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

> On March 28, 2016, 10:41 a.m., Puneet Gupta wrote: > > lens-server-api/src/main/java/org/apache/lens/server/api/common/ExponentialBackOffRetryHandler.java, > > line 61 > > > > > > Should we move all syncronization

[jira] [Commented] (LENS-993) Estimate thread pool does not grow beyond minimum pool size.

[ https://issues.apache.org/jira/browse/LENS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214095#comment-15214095 ] Hudson commented on LENS-993: - SUCCESS: Integrated in Lens-Commit-Java8 #124 (See [https://buil

[jira] [Commented] (LENS-975) Add cube-segmentation specification

[ https://issues.apache.org/jira/browse/LENS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214074#comment-15214074 ] Hudson commented on LENS-975: - FAILURE: Integrated in Lens-Commit #1213 (See [https://builds.ap

[jira] [Commented] (LENS-993) Estimate thread pool does not grow beyond minimum pool size.

[ https://issues.apache.org/jira/browse/LENS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214076#comment-15214076 ] Hudson commented on LENS-993: - FAILURE: Integrated in Lens-Commit #1213 (See [https://builds.ap

[jira] [Commented] (LENS-982) lens-ml-lib build timing out on some environments

[ https://issues.apache.org/jira/browse/LENS-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214075#comment-15214075 ] Hudson commented on LENS-982: - FAILURE: Integrated in Lens-Commit #1213 (See [https://builds.ap

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

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45207/#review125617 --- lens-server-api/src/main/java/org/apache/lens/server/api/common/E

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

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44171/#review125622 --- Fix it, then Ship it! Other changes look fine to me. lens-api

Re: Review Request 43088: LENS-939 : Add Session tests to regression

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/43088/#review125624 --- Ship it! Ship It! - Amareshwari Sriramadasu On Feb. 11, 2016

[jira] [Updated] (LENS-975) Add cube-segmentation specification

[ https://issues.apache.org/jira/browse/LENS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu updated LENS-975: - Resolution: Fixed Fix Version/s: 2.6 Status: Resolved (was: Patch

[jira] [Updated] (LENS-982) lens-ml-lib build timing out on some environments

[ https://issues.apache.org/jira/browse/LENS-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu updated LENS-982: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed myself

[jira] [Updated] (LENS-993) Estimate thread pool does not grow beyond minimum pool size.

[ https://issues.apache.org/jira/browse/LENS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu updated LENS-993: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed myself.

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

Deepak, We should call only PMC votes as Binding votes for releases. Thanks On Mon, Mar 28, 2016 at 2:23 PM, Deepak Barr wrote: > Hey all, > > Thanks all for taking time to validate the release candidate and > vote. Voting is closed now. > > Vote has passed with 7 [+1] votes and no [0]

[jira] [Commented] (LENS-993) Estimate thread pool does not grow beyond minimum pool size.

[ https://issues.apache.org/jira/browse/LENS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214045#comment-15214045 ] Amareshwari Sriramadasu commented on LENS-993: -- Builds #338 and #345 failed bec

[jira] [Commented] (LENS-982) lens-ml-lib build timing out on some environments

[ https://issues.apache.org/jira/browse/LENS-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214042#comment-15214042 ] Amareshwari Sriramadasu commented on LENS-982: -- Builds #342 and #343 failed bec

[jira] [Commented] (LENS-982) lens-ml-lib build timing out on some environments

[ https://issues.apache.org/jira/browse/LENS-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214034#comment-15214034 ] Puneet Gupta commented on LENS-982: --- +1 > lens-ml-lib build timing out on some environmen

[jira] [Updated] (LENS-918) Query Priority is not getting logged in query logs

[ https://issues.apache.org/jira/browse/LENS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puneet Gupta updated LENS-918: -- Assignee: Ajay Yadava (was: Puneet Gupta) > Query Priority is not getting logged in query logs >

[jira] [Commented] (LENS-510) change dimtable prefix to "dimtable." from "dimtble."

[ https://issues.apache.org/jira/browse/LENS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213989#comment-15213989 ] Amareshwari Sriramadasu commented on LENS-510: -- We should be able to read schem

[jira] [Commented] (LENS-40) Final Explan plan returned should include more information on why drivers are skipped

[ https://issues.apache.org/jira/browse/LENS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213986#comment-15213986 ] Amareshwari Sriramadasu commented on LENS-40: - We should go with approach #2. We

[RESULT][VOTE] Release of Apache Lens 2.5.0-beta

Hey all, Thanks all for taking time to validate the release candidate and vote. Voting is closed now. Vote has passed with 7 [+1] votes and no [0] or [-1] votes. +1 votes: Deepak Kumar Barr Raju Bairishetti Amareshwari SriRamadasu Jean-Baptiste Onofré Puneet Gupta Sushil Mohanty Ajay Yada

Re: Lens meetup in April?

+1 for 22nd April On Mon, Mar 28, 2016 at 2:01 PM, Deepak Kumar Barr (Tech_BLR) < deepak.b...@flipkart.com> wrote: > +1 for 22nd April. Will be in delhi on 15th. > > Regards, > Deepak Kumar Barr > Bigfoot-Apps > > On Mon, Mar 28, 2016 at 10:12 AM, Amareshwari Sriramdasu < > amareshw...@apache.org

Re: Lens meetup in April?

+1 for 22nd April. Will be in delhi on 15th. Regards, Deepak Kumar Barr Bigfoot-Apps On Mon, Mar 28, 2016 at 10:12 AM, Amareshwari Sriramdasu < amareshw...@apache.org> wrote: > Hi all, > > Its been long we had a meetup. Can we have a meetup some time in April? > > Shall we do it a Friday 15th or

[jira] [Commented] (LENS-975) Add cube-segmentation specification

[ https://issues.apache.org/jira/browse/LENS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213929#comment-15213929 ] Hadoop QA commented on LENS-975: Applied patch: [LENS-975-5.patch|https://issues.apache.org

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

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45207/ --- (Updated March 28, 2016, 7:33 a.m.) Review request for lens. Changes ---

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

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45207/ --- (Updated March 28, 2016, 7:26 a.m.) Review request for lens. Changes ---

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

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45207/ --- (Updated March 28, 2016, 7:22 a.m.) Review request for lens. Changes ---