[jira] [Commented] (HIVE-23129) Cast invalid string to date returns incorrect result
[
https://issues.apache.org/jira/browse/HIVE-23129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17322350#comment-17322350
]
Renukaprasad C commented on HIVE-23129:
---
[~yumwang] Thanks for reporting [~kgyrtkirk] Thanks for the feedback. In my
opinion, this is a feature inherited from JDK. Can you please have a look into
it?
> Cast invalid string to date returns incorrect result
>
>
> Key: HIVE-23129
> URL: https://issues.apache.org/jira/browse/HIVE-23129
> Project: Hive
> Issue Type: Bug
>Affects Versions: 3.1.2
>Reporter: Yuming Wang
>Assignee: wenjun ma
>Priority: Major
>
> {noformat}
> hive> select cast('2020-20-20' as date);
> OK
> 2021-08-20
> Time taken: 4.436 seconds, Fetched: 1 row(s)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (HIVE-25022) Metric about incomplete compactions
[
https://issues.apache.org/jira/browse/HIVE-25022?focusedWorklogId=583551=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-583551
]
ASF GitHub Bot logged work on HIVE-25022:
-
Author: ASF GitHub Bot
Created on: 15/Apr/21 16:04
Start Date: 15/Apr/21 16:04
Worklog Time Spent: 10m
Work Description: klcopp opened a new pull request #2184:
URL: https://github.com/apache/hive/pull/2184
### What changes were proposed in this pull request?
See https://issues.apache.org/jira/browse/HIVE-25022
### How was this patch tested?
Unit tests
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 583551)
Remaining Estimate: 0h
Time Spent: 10m
> Metric about incomplete compactions
> ---
>
> Key: HIVE-25022
> URL: https://issues.apache.org/jira/browse/HIVE-25022
> Project: Hive
> Issue Type: Sub-task
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> "Compactions in a state" metrics (for example compaction_num_working) count
> the sum of tables/partitions where the last compaction is in that state.
> I propose introducing a new metric about incomplete compactions: i.e. the
> number of tables/partitions where the last finished compaction* is
> unsuccessful (failed or "did not initiate"), or where major compaction was
> unsuccessful then minor compaction succeeded (compaction is not "complete"
> since major compaction has not succeeded in the time since it should have
> run).
> Example:
> {code:java}
> These compactions ran on a partition:
> major succeeded
> major working
> major failed
> major initiated
> major working
> major failed
> major initiated
> major working
> The "compactions in a state" metrics will consider the state of this table:
> working.
> The "incomplete compactions" metric will consider this: incomplete, since
> there have been failed compactions since the last succeeded compaction.
> {code}
> Another example:
> {code:java}
> These compactions ran on a partition:
> major succeeded
> major failed
> minor failed
> minor succeeded
> The "compactions in a state" metrics will consider the state of this table:
> succeeded.
> The "incomplete compactions" metric will consider this: incomplete, since
> there hasn't been a major succeeded since major failed.{code}
> Last example:
> {code:java}
> These compactions ran on a partition:
> major succeeded
> minor did not initiate
> The "compactions in a state" metrics will consider the state of this table:
> did not initiate.
> The "incomplete compactions" metric will consider this: incomplete, since the
> last compaction was "did not initiate"{code}
> *finished compaction: state in (succeeded, failed, attempted/did not initiate)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HIVE-25022) Metric about incomplete compactions
[
https://issues.apache.org/jira/browse/HIVE-25022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HIVE-25022:
--
Labels: pull-request-available (was: )
> Metric about incomplete compactions
> ---
>
> Key: HIVE-25022
> URL: https://issues.apache.org/jira/browse/HIVE-25022
> Project: Hive
> Issue Type: Sub-task
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> "Compactions in a state" metrics (for example compaction_num_working) count
> the sum of tables/partitions where the last compaction is in that state.
> I propose introducing a new metric about incomplete compactions: i.e. the
> number of tables/partitions where the last finished compaction* is
> unsuccessful (failed or "did not initiate"), or where major compaction was
> unsuccessful then minor compaction succeeded (compaction is not "complete"
> since major compaction has not succeeded in the time since it should have
> run).
> Example:
> {code:java}
> These compactions ran on a partition:
> major succeeded
> major working
> major failed
> major initiated
> major working
> major failed
> major initiated
> major working
> The "compactions in a state" metrics will consider the state of this table:
> working.
> The "incomplete compactions" metric will consider this: incomplete, since
> there have been failed compactions since the last succeeded compaction.
> {code}
> Another example:
> {code:java}
> These compactions ran on a partition:
> major succeeded
> major failed
> minor failed
> minor succeeded
> The "compactions in a state" metrics will consider the state of this table:
> succeeded.
> The "incomplete compactions" metric will consider this: incomplete, since
> there hasn't been a major succeeded since major failed.{code}
> Last example:
> {code:java}
> These compactions ran on a partition:
> major succeeded
> minor did not initiate
> The "compactions in a state" metrics will consider the state of this table:
> did not initiate.
> The "incomplete compactions" metric will consider this: incomplete, since the
> last compaction was "did not initiate"{code}
> *finished compaction: state in (succeeded, failed, attempted/did not initiate)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (HIVE-25022) Metric about incomplete compactions
[
https://issues.apache.org/jira/browse/HIVE-25022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Coppage reassigned HIVE-25022:
> Metric about incomplete compactions
> ---
>
> Key: HIVE-25022
> URL: https://issues.apache.org/jira/browse/HIVE-25022
> Project: Hive
> Issue Type: Sub-task
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
>
> "Compactions in a state" metrics (for example compaction_num_working) count
> the sum of tables/partitions where the last compaction is in that state.
> I propose introducing a new metric about incomplete compactions: i.e. the
> number of tables/partitions where the last finished compaction* is
> unsuccessful (failed or "did not initiate"), or where major compaction was
> unsuccessful then minor compaction succeeded (compaction is not "complete"
> since major compaction has not succeeded in the time since it should have
> run).
> Example:
> {code:java}
> These compactions ran on a partition:
> major succeeded
> major working
> major failed
> major initiated
> major working
> major failed
> major initiated
> major working
> The "compactions in a state" metrics will consider the state of this table:
> working.
> The "incomplete compactions" metric will consider this: incomplete, since
> there have been failed compactions since the last succeeded compaction.
> {code}
> Another example:
> {code:java}
> These compactions ran on a partition:
> major succeeded
> major failed
> minor failed
> minor succeeded
> The "compactions in a state" metrics will consider the state of this table:
> succeeded.
> The "incomplete compactions" metric will consider this: incomplete, since
> there hasn't been a major succeeded since major failed.{code}
> Last example:
> {code:java}
> These compactions ran on a partition:
> major succeeded
> minor did not initiate
> The "compactions in a state" metrics will consider the state of this table:
> did not initiate.
> The "incomplete compactions" metric will consider this: incomplete, since the
> last compaction was "did not initiate"{code}
> *finished compaction: state in (succeeded, failed, attempted/did not initiate)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HIVE-24396) [New Feature] Add data connector support for remote datasources
[ https://issues.apache.org/jira/browse/HIVE-24396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naveen Gangam resolved HIVE-24396. -- Fix Version/s: 4.0.0 Resolution: Fixed Initial fix has been committed to master for 4.0.0. Follow on fixes will be landing over time that adds support for additional connectors. > [New Feature] Add data connector support for remote datasources > --- > > Key: HIVE-24396 > URL: https://issues.apache.org/jira/browse/HIVE-24396 > Project: Hive > Issue Type: Improvement > Components: Hive >Reporter: Naveen Gangam >Assignee: Naveen Gangam >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0 > > Attachments: External datasources support in Hive Metastore.pdf > > Time Spent: 11h > Remaining Estimate: 0h > > This feature work is to be able to support in Hive Metastore to be able to > configure data connectors for remote datasources and map databases. We > currently have support for remote tables via StorageHandlers like > JDBCStorageHandler and HBaseStorageHandler. > Data connectors are a natural extension to this where we can map an entire > database or catalogs instead of individual tables. The tables within are > automagically mapped at runtime. The metadata for these tables are not > persisted in Hive. They are always mapped and built at runtime. > With this feature, we introduce a concept of type for Databases in Hive. > NATIVE vs REMOTE. All current databases are NATIVE. To create a REMOTE > database, the following syntax is to be used > CREATE REMOTE DATABASE remote_db USING WITH DCPROPERTIES > (); > Will attach a design doc to this jira. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-25021) Divide oldest_open_txn into oldest replication and non-replication transactions
[ https://issues.apache.org/jira/browse/HIVE-25021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antal Sinkovits reassigned HIVE-25021: -- > Divide oldest_open_txn into oldest replication and non-replication > transactions > --- > > Key: HIVE-25021 > URL: https://issues.apache.org/jira/browse/HIVE-25021 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > > We should have different metrics (age and txn id) for > oldest replication txn (TXN_TYPE==1) > oldest non-replication txn (TXN_TYPE!=1) > so recommendations can be tailored to the different cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HIVE-25021) Divide oldest_open_txn into oldest replication and non-replication transactions
[ https://issues.apache.org/jira/browse/HIVE-25021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-25021 started by Antal Sinkovits. -- > Divide oldest_open_txn into oldest replication and non-replication > transactions > --- > > Key: HIVE-25021 > URL: https://issues.apache.org/jira/browse/HIVE-25021 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > > We should have different metrics (age and txn id) for > oldest replication txn (TXN_TYPE==1) > oldest non-replication txn (TXN_TYPE!=1) > so recommendations can be tailored to the different cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-25020) Prepared statement related exceptions from Metastore when using org.mariadb.jdbc.Driver
[
https://issues.apache.org/jira/browse/HIVE-25020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Toscano updated HIVE-25020:
Description:
Hi everybody,
I am running Apache Bigtop 1.5 on Debian, and I am currently in the process of
migrating everything from Debian 9 (stretch) to 10 (buster). Part of the
upgrade involves the libmysql-dev vs libmariadb-dev packages, since the former
is not provided on Buster (hence the only jdbc driver available is
org.mariadb.jdbc.Driver).
Bigtop 1.5 ships with hive 2.3.6, Buster ships with libmariadb-java 2.3.0.
When I upgraded the hive-site.xml file with
javax.jdo.option.ConnectionDriverName=org.mariadb.jdbc.Driver I noticed some
issues on the Metastore side, for example
{code}
2021-04-13T06:46:15,564 ERROR [pool-11-thread-144]
metastore.RetryingHMSHandler: Retrying HMSHandler after 2000 ms (attempt 1 of
10) with error: javax.jdo.JDODataStoreException: Cannot set Object parameter:
value = MANAGED_TABLE for column "" : Could not set parameter at position 1
(values was 'MANAGED_TABLE')
Query - conn:30368(M) - "SELECT DISTINCT
'org.apache.hadoop.hive.metastore.model.MTable' AS
NUCLEUS_TYPE,A0.CREATE_TIME,A0.LAST_ACCESS_TIME,A0.OWNER,A0.RETENTION,A0.IS_REWRITE_ENABLED,A0.TBL_NAME,A0.TBL_TYPE,A0.TBL_ID
FROM TBLS A0 LEFT OUTER JOIN DBS B0 ON A0.DB_ID = B0.DB_ID WHERE
LOWER(B0.`NAME`) LIKE 'default' ESCAPE '\\' AND A0.TBL_TYPE = ?) OR
(A0.TBL_TYPE = ?)) OR (A0.TBL_TYPE = ?)) OR (A0.TBL_TYPE = ?))"
at
org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:543)
at org.datanucleus.api.jdo.JDOQuery.executeInternal(JDOQuery.java:391)
at org.datanucleus.api.jdo.JDOQuery.executeWithArray(JDOQuery.java:267)
at
org.apache.hadoop.hive.metastore.ObjectStore.getTableMeta(ObjectStore.java:1265)
at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:101)
at com.sun.proxy.$Proxy25.getTableMeta(Unknown Source)
at
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_table_meta(HiveMetaStore.java:2006)
at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:148)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:107)
at com.sun.proxy.$Proxy26.get_table_meta(Unknown Source)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_meta.getResult(ThriftHiveMetastore.java:11429)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_meta.getResult(ThriftHiveMetastore.java:11413)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:594)
at
org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:589)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1926)
at
org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor.process(HadoopThriftAuthBridge.java:589)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
The above was originated from Hue while trying to fetch metadata about tables
into a database. I tried to deploy libmysql-dev (stretch package deployed on
buster), reverting javax.jdo.option.ConnectionDriverName to
com.mysql.jdbc.Driver and all the issues disappeared. This is a workaround that
can work as interim solution, but I'd like to know if what I encountered above
is expected or if there is a suggested way to fix it (that could also be
included in Hive 3.x, it will be packaged in the next Bigtop version so it
would be perfectly acceptable for me).
was:
Hi everybody,
I am running Apache Bigtop 1.5 on Debian, and I am currently in the process of
migrating
[jira] [Work logged] (HIVE-25019) Rename metrics that have spaces in the name
[ https://issues.apache.org/jira/browse/HIVE-25019?focusedWorklogId=583269=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-583269 ] ASF GitHub Bot logged work on HIVE-25019: - Author: ASF GitHub Bot Created on: 15/Apr/21 10:31 Start Date: 15/Apr/21 10:31 Worklog Time Spent: 10m Work Description: asinkovits opened a new pull request #2183: URL: https://github.com/apache/hive/pull/2183 ### What changes were proposed in this pull request? Rename metrics that have spaces in the name as it can cause issues when consuming ### Why are the changes needed? Subtask is part of the compaction observability initiative. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Unit test -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 583269) Remaining Estimate: 0h Time Spent: 10m > Rename metrics that have spaces in the name > --- > > Key: HIVE-25019 > URL: https://issues.apache.org/jira/browse/HIVE-25019 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Metrics "num_compactions_ready for cleaning" and "num_compactions_not > initiated" contain spaces. > They should be renamed to "num_compactions_ready_for_cleaning" and > "num_compactions_not_initiated" respectively. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-25019) Rename metrics that have spaces in the name
[ https://issues.apache.org/jira/browse/HIVE-25019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-25019: -- Labels: pull-request-available (was: ) > Rename metrics that have spaces in the name > --- > > Key: HIVE-25019 > URL: https://issues.apache.org/jira/browse/HIVE-25019 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Metrics "num_compactions_ready for cleaning" and "num_compactions_not > initiated" contain spaces. > They should be renamed to "num_compactions_ready_for_cleaning" and > "num_compactions_not_initiated" respectively. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HIVE-25019) Rename metrics that have spaces in the name
[ https://issues.apache.org/jira/browse/HIVE-25019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-25019 started by Antal Sinkovits. -- > Rename metrics that have spaces in the name > --- > > Key: HIVE-25019 > URL: https://issues.apache.org/jira/browse/HIVE-25019 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > > Metrics "num_compactions_ready for cleaning" and "num_compactions_not > initiated" contain spaces. > They should be renamed to "num_compactions_ready_for_cleaning" and > "num_compactions_not_initiated" respectively. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-25019) Rename metrics that have spaces in the name
[ https://issues.apache.org/jira/browse/HIVE-25019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antal Sinkovits reassigned HIVE-25019: -- > Rename metrics that have spaces in the name > --- > > Key: HIVE-25019 > URL: https://issues.apache.org/jira/browse/HIVE-25019 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > > Metrics "num_compactions_ready for cleaning" and "num_compactions_not > initiated" contain spaces. > They should be renamed to "num_compactions_ready_for_cleaning" and > "num_compactions_not_initiated" respectively. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-25018) Create new metrics about Initiator / Cleaner failures
[ https://issues.apache.org/jira/browse/HIVE-25018?focusedWorklogId=583184=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-583184 ] ASF GitHub Bot logged work on HIVE-25018: - Author: ASF GitHub Bot Created on: 15/Apr/21 07:33 Start Date: 15/Apr/21 07:33 Worklog Time Spent: 10m Work Description: asinkovits opened a new pull request #2182: URL: https://github.com/apache/hive/pull/2182 ### What changes were proposed in this pull request? Introduce new ratio gauges for initiator/cleaner failures. ### Why are the changes needed? Subtask is part of the compaction observability initiative. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Unit tests were added. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 583184) Remaining Estimate: 0h Time Spent: 10m > Create new metrics about Initiator / Cleaner failures > - > > Key: HIVE-25018 > URL: https://issues.apache.org/jira/browse/HIVE-25018 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > 2 new metrics should be defined: > Failed Initiator cycles > Failed Cleaner cycles > They should be measured as part of the error handling in the services, the > lock timeout on AUX lock, should be ignored. > These should be RatioGauges (fail / success) > A RatioGauge implementation is available in the metrics package in common, a > similar one should be created in the metastore. The common is build on top of > MetricsVariable interface, where someone provides the metric from outside, in > the metastore it should be done like the Gauge implementation, where the > metrics class handles the AtomicIntegers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-25018) Create new metrics about Initiator / Cleaner failures
[ https://issues.apache.org/jira/browse/HIVE-25018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-25018: -- Labels: pull-request-available (was: ) > Create new metrics about Initiator / Cleaner failures > - > > Key: HIVE-25018 > URL: https://issues.apache.org/jira/browse/HIVE-25018 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > 2 new metrics should be defined: > Failed Initiator cycles > Failed Cleaner cycles > They should be measured as part of the error handling in the services, the > lock timeout on AUX lock, should be ignored. > These should be RatioGauges (fail / success) > A RatioGauge implementation is available in the metrics package in common, a > similar one should be created in the metastore. The common is build on top of > MetricsVariable interface, where someone provides the metric from outside, in > the metastore it should be done like the Gauge implementation, where the > metrics class handles the AtomicIntegers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HIVE-25018) Create new metrics about Initiator / Cleaner failures
[ https://issues.apache.org/jira/browse/HIVE-25018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-25018 started by Antal Sinkovits. -- > Create new metrics about Initiator / Cleaner failures > - > > Key: HIVE-25018 > URL: https://issues.apache.org/jira/browse/HIVE-25018 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > > 2 new metrics should be defined: > Failed Initiator cycles > Failed Cleaner cycles > They should be measured as part of the error handling in the services, the > lock timeout on AUX lock, should be ignored. > These should be RatioGauges (fail / success) > A RatioGauge implementation is available in the metrics package in common, a > similar one should be created in the metastore. The common is build on top of > MetricsVariable interface, where someone provides the metric from outside, in > the metastore it should be done like the Gauge implementation, where the > metrics class handles the AtomicIntegers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-25018) Create new metrics about Initiator / Cleaner failures
[ https://issues.apache.org/jira/browse/HIVE-25018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antal Sinkovits reassigned HIVE-25018: -- > Create new metrics about Initiator / Cleaner failures > - > > Key: HIVE-25018 > URL: https://issues.apache.org/jira/browse/HIVE-25018 > Project: Hive > Issue Type: Sub-task >Reporter: Antal Sinkovits >Assignee: Antal Sinkovits >Priority: Major > > 2 new metrics should be defined: > Failed Initiator cycles > Failed Cleaner cycles > They should be measured as part of the error handling in the services, the > lock timeout on AUX lock, should be ignored. > These should be RatioGauges (fail / success) > A RatioGauge implementation is available in the metrics package in common, a > similar one should be created in the metastore. The common is build on top of > MetricsVariable interface, where someone provides the metric from outside, in > the metastore it should be done like the Gauge implementation, where the > metrics class handles the AtomicIntegers -- This message was sent by Atlassian Jira (v8.3.4#803005)
