[
https://issues.apache.org/jira/browse/IMPALA-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-7564:
--
Description:
With IMPALA-5547, we predict whether a join is an FK/PK join as follows.
{noformat}
//
bharath v created IMPALA-7564:
-
Summary: Conservative FK/PK join type estimation with complex
equi-join conjuncts
Key: IMPALA-7564
URL: https://issues.apache.org/jira/browse/IMPALA-7564
Project: IMPALA
bharath v created IMPALA-7560:
-
Summary: Better selectivity estimate for != (not equals) binary
predicate
Key: IMPALA-7560
URL: https://issues.apache.org/jira/browse/IMPALA-7560
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620017#comment-16620017
]
bharath v commented on IMPALA-7560:
---
Agreed [~Paul.Rogers]. Impala tables can include stats (NDVs
[
https://issues.apache.org/jira/browse/IMPALA-7992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-7992:
-
Assignee: Csaba Ringhofer
> test_decimal_fuzz.py/test_decimal_ops failing in exhaustive runs
>
[
https://issues.apache.org/jira/browse/IMPALA-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-7994:
--
Priority: Blocker (was: Critical)
> Queries hitting memory limit issues in release builds
>
[
https://issues.apache.org/jira/browse/IMPALA-8007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725419#comment-16725419
]
bharath v commented on IMPALA-8007:
---
[~poojanilangekar] Assigning this to you since you added this
[
https://issues.apache.org/jira/browse/IMPALA-8007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725417#comment-16725417
]
bharath v commented on IMPALA-8007:
---
I think one of the problems here is that {{secs_since_heartbeat}}
[
https://issues.apache.org/jira/browse/IMPALA-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725429#comment-16725429
]
bharath v commented on IMPALA-8008:
---
[~fredyw] Mind taking a look? I'm guessing you might have some
bharath v created IMPALA-8008:
-
Summary: InvocationTargetException when making HMS RPCs
Key: IMPALA-8008
URL: https://issues.apache.org/jira/browse/IMPALA-8008
Project: IMPALA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IMPALA-7992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-7992:
-
Assignee: (was: Zoltán Borók-Nagy)
> test_decimal_fuzz.py/test_decimal_ops failing in
[
https://issues.apache.org/jira/browse/IMPALA-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-7322:
-
Assignee: Yongzhi Chen
> Add storage wait time to profile for operations with metadata load
>
[
https://issues.apache.org/jira/browse/IMPALA-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-6903:
-
Assignee: Yongzhi Chen
> Allow download of text profile via Impala WebUI
>
[
https://issues.apache.org/jira/browse/IMPALA-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-7637:
-
Assignee: Yongzhi Chen
> Include more hash table stats in profile
>
[
https://issues.apache.org/jira/browse/IMPALA-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803501#comment-16803501
]
bharath v commented on IMPALA-7864:
---
We could simply bump the number of retries but I think we should
[
https://issues.apache.org/jira/browse/IMPALA-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-8272:
-
Assignee: Yongzhi Chen
> test_catalog_tablesfilesusage failing
>
bharath v created IMPALA-8243:
-
Summary: ConcurrentModificationException in Catalog stress tests
Key: IMPALA-8243
URL: https://issues.apache.org/jira/browse/IMPALA-8243
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8243:
--
Description:
Following is the full stack from the Catalog server logs.
{noformat}
14:09:29.474424
[
https://issues.apache.org/jira/browse/IMPALA-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-7594.
---
Resolution: Duplicate
I think IMPALA-7870 fixed this. I don't think we ever ran into this after
[
https://issues.apache.org/jira/browse/IMPALA-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-6900:
-
Assignee: (was: Vuk Ercegovac)
> Invalidate metadata operation is ignored at a coordinator
[
https://issues.apache.org/jira/browse/IMPALA-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8243.
---
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> ConcurrentModificationException in Catalog
[
https://issues.apache.org/jira/browse/IMPALA-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-6234.
---
Resolution: Not A Problem
> COMPUTE INCREMENTAL STATS with partition specs fails if no partition
[
https://issues.apache.org/jira/browse/IMPALA-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16788330#comment-16788330
]
bharath v commented on IMPALA-6234:
---
I'm not able to repro this either. This is on the master.
[
https://issues.apache.org/jira/browse/IMPALA-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8174:
--
Comment: was deleted
(was: Failing build was
bharath v created IMPALA-8177:
-
Summary: Log DDL exceptions in the coordinator log [supportability]
Key: IMPALA-8177
URL: https://issues.apache.org/jira/browse/IMPALA-8177
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-7346.
---
Resolution: Duplicate
IMPALA-5872 already addresses this. Jeszy, please reopen if you think
[
https://issues.apache.org/jira/browse/IMPALA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-7961.
---
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> Concurrent catalog heavy workloads can cause
[
https://issues.apache.org/jira/browse/IMPALA-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755488#comment-16755488
]
bharath v commented on IMPALA-7034:
---
[~thundergun] This should be substantially improved with
[
https://issues.apache.org/jira/browse/IMPALA-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-3681.
---
Resolution: Duplicate
> Automatic invalidation of HMS metadata using Hive replication API
[
https://issues.apache.org/jira/browse/IMPALA-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-3547.
---
Resolution: Duplicate
This is resolved via IMPALA-7127 (and its subtasks).
> Bound the size of
[
https://issues.apache.org/jira/browse/IMPALA-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-4003.
---
Resolution: Cannot Reproduce
Not much actionable information.
> DDL statements taking too long
>
[
https://issues.apache.org/jira/browse/IMPALA-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-3605.
---
Resolution: Fixed
Not much actionable information. Some significant improvements have landed in
[
https://issues.apache.org/jira/browse/IMPALA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758860#comment-16758860
]
bharath v commented on IMPALA-7961:
---
After digging into this a bit more, the issue here seems to be a
[
https://issues.apache.org/jira/browse/IMPALA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-7961:
--
Description:
When catalog server is under heavy load with concurrent updates to objects,
queries
[
https://issues.apache.org/jira/browse/IMPALA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-7961:
--
Attachment: 0001-Repro-of-IMPALA-7961.patch
> Concurrent catalog heavy workloads can cause queries
[
https://issues.apache.org/jira/browse/IMPALA-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-7935:
-
Assignee: Anurag Mantripragada
> /catalog_object end point broken in LocalCatalog mode
>
[
https://issues.apache.org/jira/browse/IMPALA-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16818447#comment-16818447
]
bharath v commented on IMPALA-7864:
---
[~attilaj] Ack, let me dig into this and get back!
>
[
https://issues.apache.org/jira/browse/IMPALA-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8420:
--
Component/s: Clients
> Support HTTP based HS2/beeswax endpoints on coordinators
>
bharath v created IMPALA-8420:
-
Summary: Support HTTP based HS2/beeswax endpoints on coordinators
Key: IMPALA-8420
URL: https://issues.apache.org/jira/browse/IMPALA-8420
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8667:
--
Labels: ramp-up (was: )
> Remove --pull_incremental_statistics flag (on by default)
>
[
https://issues.apache.org/jira/browse/IMPALA-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-8606:
-
Assignee: bharath v
> GET_TABLES performance in local catalog mode
>
[
https://issues.apache.org/jira/browse/IMPALA-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868039#comment-16868039
]
bharath v commented on IMPALA-7615:
---
Agree with your assessment. Looks like an in place update without
[
https://issues.apache.org/jira/browse/IMPALA-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868033#comment-16868033
]
bharath v commented on IMPALA-7093:
---
I think the root cause of the problem is that, unlike other DDLs,
[
https://issues.apache.org/jira/browse/IMPALA-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821508#comment-16821508
]
bharath v commented on IMPALA-8434:
---
Nice find! Looks like a bug. Feel free to fill in the "affected
[
https://issues.apache.org/jira/browse/IMPALA-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-8606:
-
Assignee: Quanlong Huang (was: bharath v)
> GET_TABLES performance in local catalog mode
>
[
https://issues.apache.org/jira/browse/IMPALA-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8443:
--
Labels: newbie supportability (was: supportability)
> Record time spent in authorization in the
bharath v created IMPALA-8443:
-
Summary: Record time spent in authorization in the runtime profile
Key: IMPALA-8443
URL: https://issues.apache.org/jira/browse/IMPALA-8443
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823662#comment-16823662
]
bharath v commented on IMPALA-8124:
---
Yes, looks like it is racing with another metadata operation on
[
https://issues.apache.org/jira/browse/IMPALA-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825577#comment-16825577
]
bharath v commented on IMPALA-8420:
---
[~arodoni_cloudera] Yes it will. Very likely we will introduce
[
https://issues.apache.org/jira/browse/IMPALA-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825394#comment-16825394
]
bharath v commented on IMPALA-8444:
---
[~csringhofer] Nice catch. That should make it much faster.
>
[
https://issues.apache.org/jira/browse/IMPALA-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8455:
--
Affects Version/s: Impala 3.2.0
> GET_TABLE failed with InvalidStorageDescriptorException
>
[
https://issues.apache.org/jira/browse/IMPALA-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8455:
--
Component/s: Catalog
> GET_TABLE failed with InvalidStorageDescriptorException
>
[
https://issues.apache.org/jira/browse/IMPALA-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826271#comment-16826271
]
bharath v commented on IMPALA-8455:
---
This is the full stacktrace on the coordinator, for the record.
[
https://issues.apache.org/jira/browse/IMPALA-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826271#comment-16826271
]
bharath v edited comment on IMPALA-8455 at 4/25/19 5:53 PM:
This is the full
bharath v created IMPALA-8444:
-
Summary: Analysis perf regression after IMPALA-7616
Key: IMPALA-8444
URL: https://issues.apache.org/jira/browse/IMPALA-8444
Project: IMPALA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IMPALA-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8444:
--
Component/s: Frontend
> Analysis perf regression after IMPALA-7616
>
[
https://issues.apache.org/jira/browse/IMPALA-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8444:
--
Description:
The patch for IMPALA-7616 caused a performance regression in analysis time when
run in
[
https://issues.apache.org/jira/browse/IMPALA-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8444:
--
Description:
The patch for IMPALA-7616 caused a performance regression in analysis time when
run in
[
https://issues.apache.org/jira/browse/IMPALA-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-8124:
-
Assignee: Anurag Mantripragada
> Build failure: webserver/test_web_pages.py
>
[
https://issues.apache.org/jira/browse/IMPALA-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886367#comment-16886367
]
bharath v commented on IMPALA-8606:
---
[~stiga-huang] Nice find. Looks like we will still miss the table
[
https://issues.apache.org/jira/browse/IMPALA-8797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907519#comment-16907519
]
bharath v commented on IMPALA-8797:
---
[~stiga-huang] That makes sense to me.
> Blacklist "sys" and
[
https://issues.apache.org/jira/browse/IMPALA-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8872:
--
Affects Version/s: Impala 3.3.0
> SPNEGO auth failures using httpcore v4.4.1
>
bharath v created IMPALA-8872:
-
Summary: SPNEGO auth failures using httpcore v4.4.1
Key: IMPALA-8872
URL: https://issues.apache.org/jira/browse/IMPALA-8872
Project: IMPALA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IMPALA-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8864.
---
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Shell tests in http mode fail on CentOS 6
>
[
https://issues.apache.org/jira/browse/IMPALA-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8872.
---
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> SPNEGO auth failures using httpcore v4.4.1
>
[
https://issues.apache.org/jira/browse/IMPALA-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909798#comment-16909798
]
bharath v commented on IMPALA-8873:
---
This is related to my change. Will fix this.
>
[
https://issues.apache.org/jira/browse/IMPALA-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-8873:
-
Assignee: bharath v
> LdapImpalaShellTest.testShellLdapAuth failed because Python version is
[
https://issues.apache.org/jira/browse/IMPALA-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8873.
---
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> LdapImpalaShellTest.testShellLdapAuth failed
[
https://issues.apache.org/jira/browse/IMPALA-8908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8908:
--
Labels: observability ramp-up (was: )
> Bad error message when failing to connect to HTTPS endpoint
[
https://issues.apache.org/jira/browse/IMPALA-8908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921592#comment-16921592
]
bharath v commented on IMPALA-8908:
---
Looks like a simple ramp-up jira. I added the label.
> Bad error
bharath v created IMPALA-8921:
-
Summary: Use kerberos short name for ranger requests.
Key: IMPALA-8921
URL: https://issues.apache.org/jira/browse/IMPALA-8921
Project: IMPALA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IMPALA-8572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8572.
---
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> Move query hook execution to before query
[
https://issues.apache.org/jira/browse/IMPALA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8228.
---
Fix Version/s: Impala 3.4.0
Resolution: Fixed
Fixed with some caveats. See the commit
[
https://issues.apache.org/jira/browse/IMPALA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-8228:
-
Assignee: bharath v
> Support for object ownership with Ranger authorization provider
>
[
https://issues.apache.org/jira/browse/IMPALA-8932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928226#comment-16928226
]
bharath v commented on IMPALA-8932:
---
I'm running into this on my local machine.
{noformat}
File
[
https://issues.apache.org/jira/browse/IMPALA-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928183#comment-16928183
]
bharath v commented on IMPALA-8579:
---
Resolve?
> Ignore trivial alter events
>
bharath v created IMPALA-8937:
-
Summary: Fine grained table metadata loading on Catalog server
Key: IMPALA-8937
URL: https://issues.apache.org/jira/browse/IMPALA-8937
Project: IMPALA
Issue Type:
bharath v created IMPALA-8931:
-
Summary: Fe not generating lineages when event hooks are configured
Key: IMPALA-8931
URL: https://issues.apache.org/jira/browse/IMPALA-8931
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-8921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8921.
---
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> Use kerberos short name for ranger requests.
[
https://issues.apache.org/jira/browse/IMPALA-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8931.
---
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> Fe not generating lineages when event hooks
[
https://issues.apache.org/jira/browse/IMPALA-8844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8844:
--
Summary: Decouple tgt renewal thread from Keberos configuration. (was:
Decouple kinit renewal thread
bharath v created IMPALA-8844:
-
Summary: Decouple kinit renewal thread from Keberos configuration.
Key: IMPALA-8844
URL: https://issues.apache.org/jira/browse/IMPALA-8844
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8717.
---
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> impala-shell support for HiveServer2 HTTP
[
https://issues.apache.org/jira/browse/IMPALA-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904051#comment-16904051
]
bharath v commented on IMPALA-6663:
---
Sorry for the delay. They look good, let me take a look at the
[
https://issues.apache.org/jira/browse/IMPALA-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889828#comment-16889828
]
bharath v edited comment on IMPALA-8777 at 7/21/19 9:35 PM:
Can you try with
[
https://issues.apache.org/jira/browse/IMPALA-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889828#comment-16889828
]
bharath v commented on IMPALA-8777:
---
Can you try with {{auth=noSasl }}in the URL? {{beeline -u
[
https://issues.apache.org/jira/browse/IMPALA-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889828#comment-16889828
]
bharath v edited comment on IMPALA-8777 at 7/21/19 9:37 PM:
Can you try with
[
https://issues.apache.org/jira/browse/IMPALA-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890607#comment-16890607
]
bharath v commented on IMPALA-8777:
---
I think this has something to do with HIVE-4232. Beeline is
[
https://issues.apache.org/jira/browse/IMPALA-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-8777.
---
Resolution: Not A Problem
Fix Version/s: Not Applicable
> Beeline timeout to connect to
bharath v created IMPALA-8771:
-
Summary: Missing stats warning for complex type columns
Key: IMPALA-8771
URL: https://issues.apache.org/jira/browse/IMPALA-8771
Project: IMPALA
Issue Type:
[
https://issues.apache.org/jira/browse/IMPALA-8771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8771:
--
Labels: observability (was: )
> Missing stats warning for complex type columns
>
[
https://issues.apache.org/jira/browse/IMPALA-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-8772:
-
Assignee: Jiawei Wang
> Import Testcase failed for SQL without table refs
>
[
https://issues.apache.org/jira/browse/IMPALA-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888996#comment-16888996
]
bharath v commented on IMPALA-8772:
---
Yes, looks like a simple fix. Can you also include the full stack
bharath v created IMPALA-8773:
-
Summary: Automatically capture test cases for queries.
Key: IMPALA-8773
URL: https://issues.apache.org/jira/browse/IMPALA-8773
Project: IMPALA
Issue Type:
[
https://issues.apache.org/jira/browse/IMPALA-8773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8773:
--
Component/s: Frontend
> Automatically capture test cases for queries.
>
[
https://issues.apache.org/jira/browse/IMPALA-8773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8773:
--
Affects Version/s: Impala 3.2.0
> Automatically capture test cases for queries.
>
bharath v created IMPALA-8797:
-
Summary: Blacklist "sys" and "information_schema" databases from
Hive
Key: IMPALA-8797
URL: https://issues.apache.org/jira/browse/IMPALA-8797
Project: IMPALA
bharath v created IMPALA-8717:
-
Summary: impala-shell support for HiveServer2 HTTP endpoint
Key: IMPALA-8717
URL: https://issues.apache.org/jira/browse/IMPALA-8717
Project: IMPALA
Issue Type:
301 - 398 of 398 matches
Mail list logo
