[jira] [Updated] (LENS-1518) Missing self for ignore cert variable in query.py file
[ https://issues.apache.org/jira/browse/LENS-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1518: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Missing self for ignore cert variable in query.py file > -- > > Key: LENS-1518 > URL: https://issues.apache.org/jira/browse/LENS-1518 > Project: Apache Lens > Issue Type: Bug > Components: client >Reporter: Ankit Kailaswar >Assignee: Ankit Kailaswar >Priority: Major > Attachments: Lens-1518.patch > > > Self is missing for variable corresponding to ignore cert. This is causing > python query builder to fail while creating request object. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LENS-1518) Missing self for ignore cert variable in query.py file
[ https://issues.apache.org/jira/browse/LENS-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499965#comment-16499965 ] Rajat Khandelwal commented on LENS-1518: Committed. Thanks [~ankitkailaswar] > Missing self for ignore cert variable in query.py file > -- > > Key: LENS-1518 > URL: https://issues.apache.org/jira/browse/LENS-1518 > Project: Apache Lens > Issue Type: Bug > Components: client >Reporter: Ankit Kailaswar >Assignee: Ankit Kailaswar >Priority: Major > Attachments: Lens-1518.patch > > > Self is missing for variable corresponding to ignore cert. This is causing > python query builder to fail while creating request object. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LENS-1517) Python3 compatibility issues with python client
[
https://issues.apache.org/jira/browse/LENS-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499773#comment-16499773
]
Rajat Khandelwal commented on LENS-1517:
+1
> Python3 compatibility issues with python client
> ---
>
> Key: LENS-1517
> URL: https://issues.apache.org/jira/browse/LENS-1517
> Project: Apache Lens
> Issue Type: Bug
> Components: python-client
>Affects Versions: 3.0, 2.8
> Environment: Python 3.5.2
> Commit: c6423ae01a4776383f0edcd8591124ac643b9e3e
>Reporter: Michael McCarthy
>Assignee: Michael McCarthy
>Priority: Major
>
> Using the python client in Python3 fails on import:
> {noformat}
> from lens.client import LensClient
> ---
> ImportError Traceback (most recent call last)
> in ()
> > 1 from lens.client import LensClient
> /data/d1/users/ds-exp/python-virtualenvs/python3.5/src/lenspythonclient/contrib/clients/python/lens/client/__init__.py
> in ()
> 15 # limitations under the License.
> 16 #
> ---> 17 from .main import LensClient
> 18
> 19 __all__ = ['LensClient']
> /data/d1/users/ds-exp/python-virtualenvs/python3.5/src/lenspythonclient/contrib/clients/python/lens/client/main.py
> in ()
> 18
> 19 from six import string_types
> ---> 20 from .log import LensLogClient
> 21 from .session import LensSessionClient
> 22 from .query import LensQueryClient
> /data/d1/users/ds-exp/python-virtualenvs/python3.5/src/lenspythonclient/contrib/clients/python/lens/client/log.py
> in ()
> 15 # limitations under the License.
> 16 #
> ---> 17 from .auth import SpnegoAuth
> 18 import requests
> 19
> /data/d1/users/ds-exp/python-virtualenvs/python3.5/src/lenspythonclient/contrib/clients/python/lens/client/auth.py
> in ()
> 19 import subprocess
> 20 import threading
> ---> 21 from urlparse import urlparse
> 22
> 23
> ImportError: No module named 'urlparse'
> {noformat}
> This appears to be due to the fact that in Python3, {{urlparse}} is
> {{urllib.parse}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (LENS-1517) Python3 compatibility issues with python client
[
https://issues.apache.org/jira/browse/LENS-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499419#comment-16499419
]
Rajat Khandelwal commented on LENS-1517:
Hi Michael. The solution you posted seems like a hack to me. Can you look at
http://python-future.org/compatible_idioms.html#urllib-module and update patch?
> Python3 compatibility issues with python client
> ---
>
> Key: LENS-1517
> URL: https://issues.apache.org/jira/browse/LENS-1517
> Project: Apache Lens
> Issue Type: Bug
> Components: python-client
>Affects Versions: 3.0, 2.8
> Environment: Python 3.5.2
> Commit: c6423ae01a4776383f0edcd8591124ac643b9e3e
>Reporter: Michael McCarthy
>Assignee: Michael McCarthy
>Priority: Major
>
> Using the python client in Python3 fails on import:
> {noformat}
> from lens.client import LensClient
> ---
> ImportError Traceback (most recent call last)
> in ()
> > 1 from lens.client import LensClient
> /data/d1/users/ds-exp/python-virtualenvs/python3.5/src/lenspythonclient/contrib/clients/python/lens/client/__init__.py
> in ()
> 15 # limitations under the License.
> 16 #
> ---> 17 from .main import LensClient
> 18
> 19 __all__ = ['LensClient']
> /data/d1/users/ds-exp/python-virtualenvs/python3.5/src/lenspythonclient/contrib/clients/python/lens/client/main.py
> in ()
> 18
> 19 from six import string_types
> ---> 20 from .log import LensLogClient
> 21 from .session import LensSessionClient
> 22 from .query import LensQueryClient
> /data/d1/users/ds-exp/python-virtualenvs/python3.5/src/lenspythonclient/contrib/clients/python/lens/client/log.py
> in ()
> 15 # limitations under the License.
> 16 #
> ---> 17 from .auth import SpnegoAuth
> 18 import requests
> 19
> /data/d1/users/ds-exp/python-virtualenvs/python3.5/src/lenspythonclient/contrib/clients/python/lens/client/auth.py
> in ()
> 19 import subprocess
> 20 import threading
> ---> 21 from urlparse import urlparse
> 22
> 23
> ImportError: No module named 'urlparse'
> {noformat}
> This appears to be due to the fact that in Python3, {{urlparse}} is
> {{urllib.parse}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (LENS-1487) Incorrect handling of array columns in python client
[ https://issues.apache.org/jira/browse/LENS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1487: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Incorrect handling of array columns in python client > > > Key: LENS-1487 > URL: https://issues.apache.org/jira/browse/LENS-1487 > Project: Apache Lens > Issue Type: Bug > Components: client >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.8 > > Attachments: LENS-1487.2017-11-21_16:17:11.patch > > > The client is splitting the list on every character. It should be splitting > on comma. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1487) Incorrect handling of array columns in python client
[ https://issues.apache.org/jira/browse/LENS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262116#comment-16262116 ] Rajat Khandelwal commented on LENS-1487: Committed myself. > Incorrect handling of array columns in python client > > > Key: LENS-1487 > URL: https://issues.apache.org/jira/browse/LENS-1487 > Project: Apache Lens > Issue Type: Bug > Components: client >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.8 > > Attachments: LENS-1487.2017-11-21_16:17:11.patch > > > The client is splitting the list on every character. It should be splitting > on comma. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1487) Incorrect handling of array columns in python client
[ https://issues.apache.org/jira/browse/LENS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1487: --- Fix Version/s: 2.8 > Incorrect handling of array columns in python client > > > Key: LENS-1487 > URL: https://issues.apache.org/jira/browse/LENS-1487 > Project: Apache Lens > Issue Type: Bug > Components: client >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.8 > > Attachments: LENS-1487.2017-11-21_16:17:11.patch > > > The client is splitting the list on every character. It should be splitting > on comma. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1487) Incorrect handling of array columns in python client
[ https://issues.apache.org/jira/browse/LENS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1487: --- Status: Patch Available (was: Open) > Incorrect handling of array columns in python client > > > Key: LENS-1487 > URL: https://issues.apache.org/jira/browse/LENS-1487 > Project: Apache Lens > Issue Type: Bug > Components: client >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1487.2017-11-21_16:17:11.patch > > > The client is splitting the list on every character. It should be splitting > on comma. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1487) Incorrect handling of array columns in python client
[ https://issues.apache.org/jira/browse/LENS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260564#comment-16260564 ] Rajat Khandelwal commented on LENS-1487: Small enough diff. Attaching directly > Incorrect handling of array columns in python client > > > Key: LENS-1487 > URL: https://issues.apache.org/jira/browse/LENS-1487 > Project: Apache Lens > Issue Type: Bug > Components: client >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1487.2017-11-21_16:17:11.patch > > > The client is splitting the list on every character. It should be splitting > on comma. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1487) Incorrect handling of array columns in python client
[ https://issues.apache.org/jira/browse/LENS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1487: --- Attachment: LENS-1487.2017-11-21_16:17:11.patch > Incorrect handling of array columns in python client > > > Key: LENS-1487 > URL: https://issues.apache.org/jira/browse/LENS-1487 > Project: Apache Lens > Issue Type: Bug > Components: client >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1487.2017-11-21_16:17:11.patch > > > The client is splitting the list on every character. It should be splitting > on comma. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (LENS-1487) Incorrect handling of array columns in python client
Rajat Khandelwal created LENS-1487: -- Summary: Incorrect handling of array columns in python client Key: LENS-1487 URL: https://issues.apache.org/jira/browse/LENS-1487 Project: Apache Lens Issue Type: Bug Components: client Reporter: Rajat Khandelwal Assignee: Rajat Khandelwal The client is splitting the list on every character. It should be splitting on comma. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1469) Support drop partition(s) for specific update periods
[ https://issues.apache.org/jira/browse/LENS-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1469: --- Fix Version/s: 2.8 > Support drop partition(s) for specific update periods > - > > Key: LENS-1469 > URL: https://issues.apache.org/jira/browse/LENS-1469 > Project: Apache Lens > Issue Type: New Feature > Components: client, server >Reporter: Amit Khanna >Assignee: Amit Khanna > Fix For: 2.8 > > Attachments: LENS-1469.patch > > > Facilitate dropping partitions based on update period. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1469) Support drop partition(s) for specific update periods
[ https://issues.apache.org/jira/browse/LENS-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1469: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Support drop partition(s) for specific update periods > - > > Key: LENS-1469 > URL: https://issues.apache.org/jira/browse/LENS-1469 > Project: Apache Lens > Issue Type: New Feature > Components: client, server >Reporter: Amit Khanna >Assignee: Amit Khanna > Fix For: 2.8 > > Attachments: LENS-1469.patch > > > Facilitate dropping partitions based on update period. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1469) Support drop partition(s) for specific update periods
[ https://issues.apache.org/jira/browse/LENS-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218211#comment-16218211 ] Rajat Khandelwal commented on LENS-1469: Committed. Thanks [~Amit khanna] > Support drop partition(s) for specific update periods > - > > Key: LENS-1469 > URL: https://issues.apache.org/jira/browse/LENS-1469 > Project: Apache Lens > Issue Type: New Feature > Components: client, server >Reporter: Amit Khanna >Assignee: Amit Khanna > Fix For: 2.8 > > Attachments: LENS-1469.patch > > > Facilitate dropping partitions based on update period. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (LENS-1469) Support drop partition(s) for specific update periods
[ https://issues.apache.org/jira/browse/LENS-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal reassigned LENS-1469: -- Assignee: Amit Khanna > Support drop partition(s) for specific update periods > - > > Key: LENS-1469 > URL: https://issues.apache.org/jira/browse/LENS-1469 > Project: Apache Lens > Issue Type: New Feature > Components: client, server >Reporter: Amit Khanna >Assignee: Amit Khanna > Attachments: LENS-1469.patch > > > Facilitate dropping partitions based on update period. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1473) Cubevirtualfact table relative start time has incorrect config field name
[ https://issues.apache.org/jira/browse/LENS-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155532#comment-16155532 ] Rajat Khandelwal commented on LENS-1473: Committed. Thanks [~rajitha.r] > Cubevirtualfact table relative start time has incorrect config field name > - > > Key: LENS-1473 > URL: https://issues.apache.org/jira/browse/LENS-1473 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1473.patch > > > Cubevirtualfact table relative start time has incorrect config field name -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1473) Cubevirtualfact table relative start time has incorrect config field name
[ https://issues.apache.org/jira/browse/LENS-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1473: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Cubevirtualfact table relative start time has incorrect config field name > - > > Key: LENS-1473 > URL: https://issues.apache.org/jira/browse/LENS-1473 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1473.patch > > > Cubevirtualfact table relative start time has incorrect config field name -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1473) Cubevirtualfact table relative start time has incorrect config field name
[ https://issues.apache.org/jira/browse/LENS-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1473: --- Fix Version/s: 2.8 > Cubevirtualfact table relative start time has incorrect config field name > - > > Key: LENS-1473 > URL: https://issues.apache.org/jira/browse/LENS-1473 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajitha R >Assignee: Rajitha R > Fix For: 2.8 > > Attachments: LENS-1473.patch > > > Cubevirtualfact table relative start time has incorrect config field name -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154014#comment-16154014
]
Rajat Khandelwal commented on LENS-1472:
Committed myself.
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.8
>
> Attachments: LENS-1472.01.patch, LENS-1472.02.patch
>
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1472:
---
Fix Version/s: 2.8
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.8
>
> Attachments: LENS-1472.01.patch, LENS-1472.02.patch
>
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1472:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.8
>
> Attachments: LENS-1472.01.patch, LENS-1472.02.patch
>
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1471) JoinCandidate's children should not share same instance of a storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153425#comment-16153425
]
Rajat Khandelwal commented on LENS-1471:
Committed myself.
> JoinCandidate's children should not share same instance of a storage
> candidate
> ---
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.8
>
> Attachments: LENS-1471.01.patch, LENS-1471.02.patch,
> LENS-1471.03.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via {{retain}} method
> of list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1471) JoinCandidate's children should not share same instance of a storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1471:
---
Fix Version/s: 2.8
> JoinCandidate's children should not share same instance of a storage
> candidate
> ---
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.8
>
> Attachments: LENS-1471.01.patch, LENS-1471.02.patch,
> LENS-1471.03.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via {{retain}} method
> of list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1471) JoinCandidate's children should not share same instance of a storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1471:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> JoinCandidate's children should not share same instance of a storage
> candidate
> ---
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.8
>
> Attachments: LENS-1471.01.patch, LENS-1471.02.patch,
> LENS-1471.03.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via {{retain}} method
> of list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1472:
---
Attachment: LENS-1472.02.patch
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1472.01.patch, LENS-1472.02.patch
>
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152619#comment-16152619
]
Rajat Khandelwal commented on LENS-1472:
Taking patch from reviewboard and attaching
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1472.01.patch, LENS-1472.02.patch
>
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1472:
---
Attachment: LENS-1472.01.patch
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1472.01.patch
>
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152581#comment-16152581
]
Rajat Khandelwal commented on LENS-1472:
Taking patch from reviewboard and attaching
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1472.01.patch
>
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1472:
---
Status: Patch Available (was: In Progress)
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1472.01.patch
>
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Work started] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on LENS-1472 started by Rajat Khandelwal.
--
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1472) Populate sample metastore on example db is failing
[
https://issues.apache.org/jira/browse/LENS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152580#comment-16152580
]
Rajat Khandelwal commented on LENS-1472:
Created https://reviews.apache.org/r/62063/
> Populate sample metastore on example db is failing
> --
>
> Key: LENS-1472
> URL: https://issues.apache.org/jira/browse/LENS-1472
> Project: Apache Lens
> Issue Type: Bug
> Components: examples
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> {noformat}
> Error Message: Internal Server Error.:
> MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
> is not a directory or unable to create one)
> at
> org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
> at
> org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
> at
> org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
> at
> org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
> at
> org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1471) JoinCandidate's children should not share same instance of a storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152579#comment-16152579
]
Rajat Khandelwal commented on LENS-1471:
Taking patch from reviewboard and attaching
> JoinCandidate's children should not share same instance of a storage
> candidate
> ---
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1471.01.patch, LENS-1471.02.patch,
> LENS-1471.03.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via {{retain}} method
> of list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1471) JoinCandidate's children should not share same instance of a storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1471:
---
Attachment: LENS-1471.03.patch
> JoinCandidate's children should not share same instance of a storage
> candidate
> ---
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1471.01.patch, LENS-1471.02.patch,
> LENS-1471.03.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via {{retain}} method
> of list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (LENS-1472) Populate sample metastore on example db is failing
Rajat Khandelwal created LENS-1472:
--
Summary: Populate sample metastore on example db is failing
Key: LENS-1472
URL: https://issues.apache.org/jira/browse/LENS-1472
Project: Apache Lens
Issue Type: Bug
Components: examples
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal
{noformat}
Error Message: Internal Server Error.:
MetaException(message:file:/usr/local/lens/client/examples/data/sales_aggr_fact2_local4
is not a directory or unable to create one)
at
org.apache.lens.client.LensMetadataClient.translate(LensMetadataClient.java:73)
at
org.apache.lens.client.LensMetadataClient.addPartitionsToFactTable(LensMetadataClient.java:875)
at
org.apache.lens.examples.PopulateSampleMetastore.createFactPartitions(PopulateSampleMetastore.java:172)
at
org.apache.lens.examples.PopulateSampleMetastore.populateFactTables(PopulateSampleMetastore.java:196)
at
org.apache.lens.examples.PopulateSampleMetastore.populateAll(PopulateSampleMetastore.java:84)
at
org.apache.lens.examples.PopulateSampleMetastore.main(PopulateSampleMetastore.java:71)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1471) JoinCandidate's children should not share same instance of a storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1471:
---
Attachment: LENS-1471.02.patch
> JoinCandidate's children should not share same instance of a storage
> candidate
> ---
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1471.01.patch, LENS-1471.02.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via {{retain}} method
> of list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1471) JoinCandidate's children should not share same instance of a storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152490#comment-16152490
]
Rajat Khandelwal commented on LENS-1471:
Taking patch from reviewboard and attaching
> JoinCandidate's children should not share same instance of a storage
> candidate
> ---
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1471.01.patch, LENS-1471.02.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via {{retain}} method
> of list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1471) JoinCandidate's children should not share same instance of a storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1471:
---
Description: The issue is in Join candidates of the kind
{{Join\[Union\[a,b\]; Union\[a,c\]\]}}. If the instance of {{a}} is shared in
different trees of a JoinCandidate, the rewritten query will be wrong.
JoinCandidate's children set exclusive measure phrase indices, and that is done
via {{retain}} method of list. So let's say union1 is answering {{\[0,1\]}}
measures and union2 is answering {{\[2,3\]}} measures, and since
{{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
no measures at all (was: The issue is in Join candidates of the kind
{{Join\[Union\[a,b\]; Union\[a,c\]\]}}. If the instance of {{a}} is shared in
different trees of a JoinCandidate, the rewritten query will be wrong.
JoinCandidate's children set exclusive measure phrase indices, and that is done
via truncate method of list. So let's say union1 is answering {{\[0,1\]}}
measures and union2 is answering {{\[2,3\]}} measures, and since
{{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
no measures at all)
> JoinCandidate's children should not share same instance of a storage
> candidate
> ---
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1471.01.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via {{retain}} method
> of list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1471) JoinCandidate's children should not share same storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1471:
---
Attachment: LENS-1471.01.patch
> JoinCandidate's children should not share same storage candidate
> -
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1471.01.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via truncate method of
> list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1471) JoinCandidate's children should not share same storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1471:
---
Status: Patch Available (was: In Progress)
> JoinCandidate's children should not share same storage candidate
> -
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1471.01.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via truncate method of
> list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1471) JoinCandidate's children should not share same storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152474#comment-16152474
]
Rajat Khandelwal commented on LENS-1471:
Taking patch from reviewboard and attaching
> JoinCandidate's children should not share same storage candidate
> -
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1471.01.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via truncate method of
> list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Work started] (LENS-1471) JoinCandidate's children should not share same storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on LENS-1471 started by Rajat Khandelwal.
--
> JoinCandidate's children should not share same storage candidate
> -
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via truncate method of
> list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1471) JoinCandidate's children should not share same instance of a storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1471:
---
Summary: JoinCandidate's children should not share same instance of a
storage candidate (was: JoinCandidate's children should not share same
storage candidate )
> JoinCandidate's children should not share same instance of a storage
> candidate
> ---
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1471.01.patch
>
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via truncate method of
> list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1471) JoinCandidate's children should not share same storage candidate
[
https://issues.apache.org/jira/browse/LENS-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152472#comment-16152472
]
Rajat Khandelwal commented on LENS-1471:
Created https://reviews.apache.org/r/62060/
> JoinCandidate's children should not share same storage candidate
> -
>
> Key: LENS-1471
> URL: https://issues.apache.org/jira/browse/LENS-1471
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
> Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
> JoinCandidate, the rewritten query will be wrong. JoinCandidate's children
> set exclusive measure phrase indices, and that is done via truncate method of
> list. So let's say union1 is answering {{\[0,1\]}} measures and union2 is
> answering {{\[2,3\]}} measures, and since
> {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\]) == \[\]}}, it ends up answering
> no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (LENS-1471) JoinCandidate's children should not share same storage candidate
Rajat Khandelwal created LENS-1471:
--
Summary: JoinCandidate's children should not share same storage
candidate
Key: LENS-1471
URL: https://issues.apache.org/jira/browse/LENS-1471
Project: Apache Lens
Issue Type: Bug
Components: cube
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal
The issue is in Join candidates of the kind {{Join\[Union\[a,b\];
Union\[a,c\]\]}}. If the instance of {{a}} is shared in different trees of a
JoinCandidate, the rewritten query will be wrong. JoinCandidate's children set
exclusive measure phrase indices, and that is done via truncate method of list.
So let's say union1 is answering {{\[0,1\]}} measures and union2 is answering
{{\[2,3\]}} measures, and since {{\[0,1,2,3\].retain(\[0,1\]).retain(\[2,3\])
== \[\]}}, it ends up answering no measures at all
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment
[
https://issues.apache.org/jira/browse/LENS-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152121#comment-16152121
]
Rajat Khandelwal commented on LENS-1439:
Committed myself.
> Having clause getting skipped if query goes to a segmentation containing
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7, 2.8
>
> Attachments: LENS-1439.01.patch, LENS-1439.01.patch,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment
[
https://issues.apache.org/jira/browse/LENS-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1439:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Having clause getting skipped if query goes to a segmentation containing
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7, 2.8
>
> Attachments: LENS-1439.01.patch, LENS-1439.01.patch,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment
[
https://issues.apache.org/jira/browse/LENS-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1439:
---
Fix Version/s: 2.8
> Having clause getting skipped if query goes to a segmentation containing
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7, 2.8
>
> Attachments: LENS-1439.01.patch, LENS-1439.01.patch,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151799#comment-16151799
]
Rajat Khandelwal commented on LENS-1468:
Committed myself.
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.8
>
> Attachments: LENS-1468.01.patch, LENS-1468.02.patch
>
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1468:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.8
>
> Attachments: LENS-1468.01.patch, LENS-1468.02.patch
>
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1468:
---
Fix Version/s: 2.8
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.8
>
> Attachments: LENS-1468.01.patch, LENS-1468.02.patch
>
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147361#comment-16147361
]
Rajat Khandelwal commented on LENS-1468:
Taking patch from reviewboard and attaching
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1468.01.patch, LENS-1468.02.patch
>
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1468:
---
Attachment: LENS-1468.02.patch
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1468.01.patch, LENS-1468.02.patch
>
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147317#comment-16147317
]
Rajat Khandelwal commented on LENS-1468:
Taking patch from reviewboard and attaching
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1468.01.patch
>
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1468:
---
Attachment: LENS-1468.01.patch
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1468.01.patch
>
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1468:
---
Status: Patch Available (was: In Progress)
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Attachments: LENS-1468.01.patch
>
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Work started] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on LENS-1468 started by Rajat Khandelwal.
--
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
[
https://issues.apache.org/jira/browse/LENS-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147315#comment-16147315
]
Rajat Khandelwal commented on LENS-1468:
Created https://reviews.apache.org/r/61992/
> Expressions in having clauses are not getting rewritten properly for join
> queries
> -
>
> Key: LENS-1468
> URL: https://issues.apache.org/jira/browse/LENS-1468
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
>
> The issue is not seen in test cases yet since somehow the order of child
> candidates in {{JoinCandidate}} has been fixed. We have observed the order
> being non-deterministic in production. And in one ordering, having clause
> works fine and in another it doesn't. Will be adding test cases to reproduce
> this issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (LENS-1468) Expressions in having clauses are not getting rewritten properly for join queries
Rajat Khandelwal created LENS-1468:
--
Summary: Expressions in having clauses are not getting rewritten
properly for join queries
Key: LENS-1468
URL: https://issues.apache.org/jira/browse/LENS-1468
Project: Apache Lens
Issue Type: Bug
Components: cube
Reporter: Rajat Khandelwal
Assignee: Rajat Khandelwal
The issue is not seen in test cases yet since somehow the order of child
candidates in {{JoinCandidate}} has been fixed. We have observed the order
being non-deterministic in production. And in one ordering, having clause works
fine and in another it doesn't. Will be adding test cases to reproduce this
issue and the fix as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1467: --- Resolution: Fixed Status: Resolved (was: Patch Available) > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1467.01.patch, LENS-1467.02.patch, > LENS-1467.03.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147048#comment-16147048 ] Rajat Khandelwal commented on LENS-1467: Committed myself. > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1467.01.patch, LENS-1467.02.patch, > LENS-1467.03.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1467: --- Fix Version/s: 2.7 > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1467.01.patch, LENS-1467.02.patch, > LENS-1467.03.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1465) Sync queries blocking threads
[ https://issues.apache.org/jira/browse/LENS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1465: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Sync queries blocking threads > - > > Key: LENS-1465 > URL: https://issues.apache.org/jira/browse/LENS-1465 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1465.01.patch > > > Sync queries taking more time than timeout are blocking threads due to a > deadlock. Each sync query is blocking one thread from jdbc execution pool and > one thread from query completion pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1465) Sync queries blocking threads
[ https://issues.apache.org/jira/browse/LENS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1465: --- Fix Version/s: 2.7 > Sync queries blocking threads > - > > Key: LENS-1465 > URL: https://issues.apache.org/jira/browse/LENS-1465 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1465.01.patch > > > Sync queries taking more time than timeout are blocking threads due to a > deadlock. Each sync query is blocking one thread from jdbc execution pool and > one thread from query completion pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1465) Sync queries blocking threads
[ https://issues.apache.org/jira/browse/LENS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147046#comment-16147046 ] Rajat Khandelwal commented on LENS-1465: Committed myself. > Sync queries blocking threads > - > > Key: LENS-1465 > URL: https://issues.apache.org/jira/browse/LENS-1465 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1465.01.patch > > > Sync queries taking more time than timeout are blocking threads due to a > deadlock. Each sync query is blocking one thread from jdbc execution pool and > one thread from query completion pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1464: --- Resolution: Fixed Status: Resolved (was: Patch Available) > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1464.01.patch, LENS-1464.02.patch, > LENS-1464.03.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147043#comment-16147043 ] Rajat Khandelwal commented on LENS-1464: Committed myself. > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1464.01.patch, LENS-1464.02.patch, > LENS-1464.03.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146971#comment-16146971 ] Rajat Khandelwal commented on LENS-1467: Taking patch from reviewboard and attaching > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1467.01.patch, LENS-1467.02.patch, > LENS-1467.03.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1467: --- Attachment: LENS-1467.03.patch > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1467.01.patch, LENS-1467.02.patch, > LENS-1467.03.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1464: --- Attachment: LENS-1464.03.patch > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1464.01.patch, LENS-1464.02.patch, > LENS-1464.03.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146945#comment-16146945 ] Rajat Khandelwal commented on LENS-1464: Taking patch from reviewboard and attaching > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1464.01.patch, LENS-1464.02.patch, > LENS-1464.03.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1467: --- Attachment: LENS-1467.02.patch > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1467.01.patch, LENS-1467.02.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-1467 started by Rajat Khandelwal. -- > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1467.01.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143796#comment-16143796 ] Rajat Khandelwal commented on LENS-1467: Taking patch from reviewboard and attaching > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1467.01.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143794#comment-16143794 ] Rajat Khandelwal commented on LENS-1467: Created https://reviews.apache.org/r/61942/ > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1467.01.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
[ https://issues.apache.org/jira/browse/LENS-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1467: --- Attachment: LENS-1467.01.patch > CubeQueryContext.getAllFilters is returning incorrect list of filters in case > there is an "OR" in the filters > - > > Key: LENS-1467 > URL: https://issues.apache.org/jira/browse/LENS-1467 > Project: Apache Lens > Issue Type: Bug > Components: cube >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1467.01.patch > > > "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed > together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (LENS-1467) CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters
Rajat Khandelwal created LENS-1467: -- Summary: CubeQueryContext.getAllFilters is returning incorrect list of filters in case there is an "OR" in the filters Key: LENS-1467 URL: https://issues.apache.org/jira/browse/LENS-1467 Project: Apache Lens Issue Type: Bug Components: cube Reporter: Rajat Khandelwal Assignee: Rajat Khandelwal "a and (b or c)" is converted to ["a", "b", "c"] which are then ANDed together, which is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1464: --- Attachment: LENS-1464.02.patch > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1464.01.patch, LENS-1464.02.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143740#comment-16143740 ] Rajat Khandelwal commented on LENS-1464: Taking patch from reviewboard and attaching > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1464.01.patch, LENS-1464.02.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1465) Sync queries blocking threads
[ https://issues.apache.org/jira/browse/LENS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143629#comment-16143629 ] Rajat Khandelwal commented on LENS-1465: Taking patch from reviewboard and attaching > Sync queries blocking threads > - > > Key: LENS-1465 > URL: https://issues.apache.org/jira/browse/LENS-1465 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1465.01.patch > > > Sync queries taking more time than timeout are blocking threads due to a > deadlock. Each sync query is blocking one thread from jdbc execution pool and > one thread from query completion pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1465) Sync queries blocking threads
[ https://issues.apache.org/jira/browse/LENS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1465: --- Status: Patch Available (was: In Progress) > Sync queries blocking threads > - > > Key: LENS-1465 > URL: https://issues.apache.org/jira/browse/LENS-1465 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1465.01.patch > > > Sync queries taking more time than timeout are blocking threads due to a > deadlock. Each sync query is blocking one thread from jdbc execution pool and > one thread from query completion pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1465) Sync queries blocking threads
[ https://issues.apache.org/jira/browse/LENS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1465: --- Attachment: LENS-1465.01.patch > Sync queries blocking threads > - > > Key: LENS-1465 > URL: https://issues.apache.org/jira/browse/LENS-1465 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1465.01.patch > > > Sync queries taking more time than timeout are blocking threads due to a > deadlock. Each sync query is blocking one thread from jdbc execution pool and > one thread from query completion pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (LENS-1465) Sync queries blocking threads
[ https://issues.apache.org/jira/browse/LENS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-1465 started by Rajat Khandelwal. -- > Sync queries blocking threads > - > > Key: LENS-1465 > URL: https://issues.apache.org/jira/browse/LENS-1465 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > > Sync queries taking more time than timeout are blocking threads due to a > deadlock. Each sync query is blocking one thread from jdbc execution pool and > one thread from query completion pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1465) Sync queries blocking threads
[ https://issues.apache.org/jira/browse/LENS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143627#comment-16143627 ] Rajat Khandelwal commented on LENS-1465: Created https://reviews.apache.org/r/61936/ > Sync queries blocking threads > - > > Key: LENS-1465 > URL: https://issues.apache.org/jira/browse/LENS-1465 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > > Sync queries taking more time than timeout are blocking threads due to a > deadlock. Each sync query is blocking one thread from jdbc execution pool and > one thread from query completion pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (LENS-1465) Sync queries blocking threads
Rajat Khandelwal created LENS-1465: -- Summary: Sync queries blocking threads Key: LENS-1465 URL: https://issues.apache.org/jira/browse/LENS-1465 Project: Apache Lens Issue Type: Bug Components: server Reporter: Rajat Khandelwal Assignee: Rajat Khandelwal Sync queries taking more time than timeout are blocking threads due to a deadlock. Each sync query is blocking one thread from jdbc execution pool and one thread from query completion pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1464: --- Attachment: LENS-1464.01.patch > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1464.01.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143612#comment-16143612 ] Rajat Khandelwal commented on LENS-1464: Created https://reviews.apache.org/r/61934/ > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1464.01.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143613#comment-16143613 ] Rajat Khandelwal commented on LENS-1464: Taking patch from reviewboard and attaching > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1464.01.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LENS-1464 started by Rajat Khandelwal. -- > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1464.01.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
[ https://issues.apache.org/jira/browse/LENS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal updated LENS-1464: --- Status: Patch Available (was: In Progress) > One or two queued queries failing with ConcurrentModificationException on > restart > -- > > Key: LENS-1464 > URL: https://issues.apache.org/jira/browse/LENS-1464 > Project: Apache Lens > Issue Type: Bug > Components: server >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Attachments: LENS-1464.01.patch > > > Happens because of synchronizations issues. If two queries are simultaneously > launching, both try to add resources to hive driver. One of those queries can > fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (LENS-1464) One or two queued queries failing with ConcurrentModificationException on restart
Rajat Khandelwal created LENS-1464: -- Summary: One or two queued queries failing with ConcurrentModificationException on restart Key: LENS-1464 URL: https://issues.apache.org/jira/browse/LENS-1464 Project: Apache Lens Issue Type: Bug Components: server Reporter: Rajat Khandelwal Assignee: Rajat Khandelwal Happens because of synchronizations issues. If two queries are simultaneously launching, both try to add resources to hive driver. One of those queries can fail then. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1373) Specify chain of comparators in lensserver-default.xml
[ https://issues.apache.org/jira/browse/LENS-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal closed LENS-1373. -- Available in https://github.com/apache/lens/blob/29568fa3999642d017977b5dda3d7e08bee91337/lens-server/src/main/resources/lensserver-default.xml#L948 > Specify chain of comparators in lensserver-default.xml > -- > > Key: LENS-1373 > URL: https://issues.apache.org/jira/browse/LENS-1373 > Project: Apache Lens > Issue Type: Task >Affects Versions: 2.7 >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1373.2016-11-07_17:09:24.patch, > LENS-1373.2016-11-07_17:30:06.patch, LENS-1373.2016-11-07_17:49:30.patch, > LENS-1373.2017-01-18_18:22:59.patch > > > Queries are compared in the following order: > 1. More retries first > 2. Higher priority first > 3. FIFO > The default value is added in code, but not in lensserver-defaults.xml. > Adding to either places should have been enough but seems like that's not > happening. Will investigate more and raise another bug if that's the case. > This jira is just for adding the defaults in xml file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1359) Add driver hooks for user based filtering of queries
[ https://issues.apache.org/jira/browse/LENS-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal closed LENS-1359. -- Verified to be working. > Add driver hooks for user based filtering of queries > > > Key: LENS-1359 > URL: https://issues.apache.org/jira/browse/LENS-1359 > Project: Apache Lens > Issue Type: Task >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Labels: incompatible > Fix For: 2.7 > > Attachments: LENS-1359.01.patch, LENS-1359.02.patch, > LENS-1359.03.patch, LENS-1359.04.patch, LENS-1359.05.patch, > LENS-1359.06.patch, LENS-1359.07.patch, LENS-1359.08.patch, > LENS-1359.09.patch, LENS-1359.10.patch, LENS-1359.11.patch, > LENS-1359.12.patch, LENS-1359.13.patch, LENS-1359.14.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1302) Add launch rejection reason to query status message
[ https://issues.apache.org/jira/browse/LENS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal closed LENS-1302. -- Able to see rejection message in the status of queued queries. Closing > Add launch rejection reason to query status message > --- > > Key: LENS-1302 > URL: https://issues.apache.org/jira/browse/LENS-1302 > Project: Apache Lens > Issue Type: Improvement >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment
[
https://issues.apache.org/jira/browse/LENS-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134956#comment-16134956
]
Rajat Khandelwal commented on LENS-1439:
[~amareshwari] Added in latest patch.
> Having clause getting skipped if query goes to a segmentation containing
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1439.01.patch, LENS-1439.01.patch,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment
[
https://issues.apache.org/jira/browse/LENS-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajat Khandelwal updated LENS-1439:
---
Attachment: LENS-1439.02.patch
> Having clause getting skipped if query goes to a segmentation containing
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1439.01.patch, LENS-1439.01.patch,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1439) Having clause getting skipped if query goes to a segmentation containing single segment
[
https://issues.apache.org/jira/browse/LENS-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134863#comment-16134863
]
Rajat Khandelwal commented on LENS-1439:
Taking patch from reviewboard and attaching
> Having clause getting skipped if query goes to a segmentation containing
> single segment
> ---
>
> Key: LENS-1439
> URL: https://issues.apache.org/jira/browse/LENS-1439
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
>Reporter: Rajat Khandelwal
>Assignee: Rajat Khandelwal
> Fix For: 2.7
>
> Attachments: LENS-1439.01.patch, LENS-1439.01.patch,
> LENS-1439.02.patch
>
>
> The condition of {{setHaving(null)}} is wrong in singleCandidatehqlcontext
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (LENS-1461) Lens services state are not persisted correctly
[
https://issues.apache.org/jira/browse/LENS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16132917#comment-16132917
]
Rajat Khandelwal commented on LENS-1461:
bq. session timeout for lens and hive are 1 day and 3 days respectievely. For a
session which is 2 days old session manager returns valid object for
HiveSession but its no longer a instance of "LensSessionImpl" since lens
session already expired. causing downcasting to initialize lens related member
variable(LensSessionHandle, db, username, password etc) to null causing
deserializer to fail for them.
Not sure what you mean by this here. By my understanding, when {{LensServices}}
is {{init}}ed, {{CLIService}} and {{CLIService.SessionManager}} are also
{{init}}ed. In the {{init}} phase of {{SessionManager}}, session impl class is
decided. That is configured to be {{LensSessionImpl.class}} in all the restarts
of the Lens Server.
What I am worried about though, is why the function
{{org.apache.lens.server.api.session.SessionService#restoreSession}} has no
usages in the project.
bq. 2. downcasting is done in getsession() method in *LensSessionImpl* and
referenced at lot of places. That might be causing other bugs apart from
mentioned above.
I assume you are talking about
{{org.apache.lens.server.BaseLensService#getSession}}. {{getSession}} has
another problem, it is throwing Jersey client exception. That exception is fine
if it ends up to user facing api classes. But it's wrong if it is being thrown
inside init/start phases. The two kind of usages' need to be served by two
different functions.
> Lens services state are not persisted correctly
> ---
>
> Key: LENS-1461
> URL: https://issues.apache.org/jira/browse/LENS-1461
> Project: Apache Lens
> Issue Type: Bug
> Components: server
>Reporter: Ankit Kailaswar
>Assignee: Ankit Kailaswar
>
> Lens services state are not persisted correctly causing lens to fail at
> startup.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (LENS-1322) Display join chain details as a tooltip on dim attributes using that join chain
[ https://issues.apache.org/jira/browse/LENS-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal closed LENS-1322. -- > Display join chain details as a tooltip on dim attributes using that join > chain > --- > > Key: LENS-1322 > URL: https://issues.apache.org/jira/browse/LENS-1322 > Project: Apache Lens > Issue Type: Improvement > Components: UI >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1322.02.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1303) list of queries on ui should use time filters
[ https://issues.apache.org/jira/browse/LENS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal closed LENS-1303. -- > list of queries on ui should use time filters > - > > Key: LENS-1303 > URL: https://issues.apache.org/jira/browse/LENS-1303 > Project: Apache Lens > Issue Type: Improvement >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1303.04.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (LENS-1344) Make individual component headers on cube schema page left aligned
[ https://issues.apache.org/jira/browse/LENS-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Khandelwal closed LENS-1344. -- > Make individual component headers on cube schema page left aligned > -- > > Key: LENS-1344 > URL: https://issues.apache.org/jira/browse/LENS-1344 > Project: Apache Lens > Issue Type: Task > Components: UI >Reporter: Rajat Khandelwal >Assignee: Rajat Khandelwal > Fix For: 2.7 > > Attachments: LENS-1344.2016-10-03_13:43:34.patch > > > Currently they are center aligned. Which has an issue in case one of the rows > is too wide. The width of the entire section is maximun of the widths of > individual rows. In case one row is too large, then the header appears in the > center of that area, which is not in visible section by default. Making it > left aligned would solve that problem -- This message was sent by Atlassian JIRA (v6.4.14#64029)
