March 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-13888) Allow custom SQL loggers by subclassing SqlStatementLogger

by Ivan Březina (JIRA)

Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzgyZWQ0MDA5... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiMzgyZW... ) HHH-13888 ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiMzgyZW... ) Allow custom SQL loggers by subclassing SqlStatementLogger ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiMzgyZW... ) Change By: Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) Logging of slow SQLs from Hibernate is a cool feature, but it would be even better if you added custom loggers. By adding setSqlStatementLogger into JdbcServices. The background: * it is not guaranteed that calling Statement.toString() will return actual SQL statement. For example Oracle's data replay datasource generates instances of proxy for TxnReplayableStatement. This class implements java.sql.Statement interface but toString() returns hexadecimal number. * as a DBA I face situations where I need to correlate customer's action which slow running query. A custom logger can be extended and can also use Thread context to log slow SQL together with applications request id. * Oracle internally identifies SQL by hash string called SQL_ID (last 8 bytes from MD5 checksum). For me it is hard to to translate fragments of SQLs logged into SQL_ID. But I can implement custom logger, which can compute and log the same SQL_ID log it also on application's side. The is a link to sample POC: [https://github.com/ibre5041/ucptest/tree/master/standalone-jpa/src/main/j...] The class * CustomSqlStatementLogger uses several reflection steps to get SQL from datatype TxnReplayableStatement. It also contains example how SQL_ID is computed. * AppHibernate is a sample application which uses Oracle's UCP connection pool and uses reflection to replace instance of SqlStatementLogger with CustomSqlStatementLogger. At the end to the app logs something like this: {{ SlowQuery: 2582 milliseconds. SQL_ID: 'bd4aqyt8dzfvf' }} The rest about the query I can find in Oracle's Active session history: \{\{SQL> select sql_text from gv$SQL where sql_id = ‘bd4aqyt8dzfvf’; }} \{\{SQL_TEXT }} \{\{select bookentity0_.id as id1_0_0_, bookentity0_.author as author2_0_0_, bookentity0_.name as name3_0_0_ from BOOK bookentity0_ where bookentity0_.id=:1 }} So practically I need to add setSqlStatementLogger and setSqlExceptionHelper to jdbcService. (or some config option identifying a class used to format SQLs logged by Hibernate). ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:d2b7993 )

5 years, 6 months

1
0
0 / 0

[JIRA] (HHH-13888) Allow custom SQL loggers by subclassing SqlStatementLogger

by Ivan Březina (JIRA)

Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNmViOTU1YTc0... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiNmViOT... ) HHH-13888 ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiNmViOT... ) Allow custom SQL loggers by subclassing SqlStatementLogger ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiNmViOT... ) Change By: Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) Logging of slow SQLs from Hibernate is a cool feature, but it would be even better if you added custom loggers. By adding setSqlStatementLogger into JdbcServices. The background: * it is not guaranteed that calling Statement.toString() will return actual SQL statement. For example Oracle's data replay datasource generates instances of proxy for TxnReplayableStatement. This class implements java.sql.Statement interface but toString() returns hexadecimal number. * as a DBA I face situations where I need to correlate customer's action which slow running query. A custom logger can be extended and can also use Thread context to log slow SQL together with applications request id. * Oracle internally identifies SQL by hash string called SQL_ID (last 8 bytes from MD5 checksum). For me it is hard to to translate fragments of SQLs logged into SQL_ID. But I can implement custom logger, which can compute and log the same SQL_ID log it also on application's side. The is a link to sample POC: [https://github.com/ibre5041/ucptest/tree/master/standalone-jpa/src/main/j...] The class * CustomSqlStatementLogger used uses several reflection steps to get SQL from datatype TxnReplayableStatement. It also contains sample example how SQL_ID is computed. * AppHibernate is a sample application which uses Oracle's UCP connection pool and uses reflection to replace instance of SqlStatementLogger with CustomSqlStatementLogger. At the end to logs something like this: {{ SlowQuery: 2582 milliseconds. SQL_ID: 'bd4aqyt8dzfvf' }} The rest about the query I can find in Oracle's Active session history: \{\{SQL> select sql_text from gv$SQL where sql_id = ‘bd4aqyt8dzfvf’; }} \{\{SQL_TEXT }} \{\{select bookentity0_.id as id1_0_0_, bookentity0_.author as author2_0_0_, bookentity0_.name as name3_0_0_ from BOOK bookentity0_ where bookentity0_.id=:1 }} So practically I need to add setSqlStatementLogger and setSqlExceptionHelper to jdbcService. (or some config option identifying a class used to format SQLs logged by Hibernate). ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:d2b7993 )

5 years, 6 months

1
0
0 / 0

[JIRA] (HHH-13888) Allow custom SQL loggers by subclassing SqlStatementLogger

by Ivan Březina (JIRA)

Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjM2NWNkZWE1... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiZjM2NW... ) HHH-13888 ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiZjM2NW... ) Allow custom SQL loggers by subclassing SqlStatementLogger ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiZjM2NW... ) Change By: Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) Logging of slow SQLs from Hibernate is a cool feature, but it would be even better if you added custom loggers. By adding setSqlStatementLogger into JdbcServices. The background: * it is not guaranteed that calling Statement.toString() will return actual SQL statement. For example Oracle's data replay datasource generates instances of proxy for TxnReplayableStatement. This class implements java.sql.Statement interface but toString() returns hexadecimal number. * as a DBA I face situations where I need to correlate customer's action which slow running query. A custom logger can be extended and can also use Thread context to log slow SQL together with applications request id. * Oracle internally identifies SQL by hash string called SQL_ID (last 8 bytes from MD5 checksum). For me it is hard to to translate fragments of SQLs logged into SQL_ID. But I can implement custom logger, which can compute and log the same SQL_ID log it also on application's side. The is a link to sample POC: [https://github.com/ibre5041/ucptest/tree/master/standalone-jpa/src/main/j...] The class * CustomSqlStatementLogger used several reflection steps to get SQL from datatype TxnReplayableStatement. It also contains sample how SQL_ID is computed. * AppHibernate is a sample application which uses Oracle's UCP connection pool and uses reflection to replace instance of SqlStatementLogger with CustomSqlStatementLogger. At the end to logs something like this: {{ SlowQuery: 2582 milliseconds. SQL_ID: 'bd4aqyt8dzfvf' }} The rest about the query I can find in Oracle's Active session history: \{\{SQL> select sql_text from gv$SQL where sql_id = ‘bd4aqyt8dzfvf’; }} \{\{ SQL_TEXT }} \{\{ select bookentity0_.id as id1_0_0_, bookentity0_.author as author2_0_0_, bookentity0_.name as name3_0_0_ from BOOK bookentity0_ where bookentity0_.id=:1 }} So practically I need to add setSqlStatementLogger and setSqlExceptionHelper to jdbcService. (or some config option identifying a class used to format SQLs logged by Hibernate). ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:d2b7993 )

5 years, 6 months

1
0
0 / 0

[JIRA] (HHH-13888) Allow custom SQL loggers by subclassing SqlStatementLogger

by Ivan Březina (JIRA)

5 years, 6 months

1
0
0 / 0

[JIRA] (HHH-13888) Allow custom SQL loggers by subclassing SqlStatementLogger

by Ivan Březina (JIRA)

Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTRlZmQ2ZTcx... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiNTRlZm... ) HHH-13888 ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiNTRlZm... ) Allow custom SQL loggers by subclassing SqlStatementLogger ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiNTRlZm... ) Change By: Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) Logging of slow SQLs from Hibernate is a cool feature, but it would be even better if you added custom loggers. By adding setSqlStatementLogger into JdbcServices. The background: - * it is not guaranteed that calling Statement.toString() will return actual SQL statement. For example Oracle's data replay datasource generates instances of proxy for TxnReplayableStatement. This class implements java.sql.Statement interface but toString() returns hexadecimal number. - * as a DBA I face situations where I need to correlate customer's action which slow running query. A custom logger can be extended and can also use Thread context to log slow SQL together with applications request id. - * Oracle internally identifies SQL by hash string called SQL_ID (last 8 bytes from MD5 checksum). For me it is hard to to translate fragments of SQLs logged into SQL_ID. But I can implement custom logger, which can compute and log the same SQL_ID log it also on application's side. The is a link to sample POC: [https://github.com/ibre5041/ucptest/tree/master/standalone-jpa/src/main/j...] The class * CustomSqlStatementLogger used several reflection steps to get SQL from datatype TxnReplayableStatement. It also contains sample how SQL_ID is computed. * AppHibernate is a sample application which uses Oracle's UCP connection pool and uses reflection to replace instance of SqlStatementLogger with CustomSqlStatementLogger. At the end to logs something like this: {{ SlowQuery: 2582 milliseconds. SQL_ID: 'bd4aqyt8dzfvf' }} The rest about the query I can find in Oracle's Active session history: \ { \ {SQL> select sql_text from gv$SQL where sql_id = ‘bd4aqyt8dzfvf’; SQL_TEXT select bookentity0_.id as id1_0_0_, bookentity0_.author as author2_0_0_, bookentity0_.name as name3_0_0_ from BOOK bookentity0_ where bookentity0_.id=:1 }} So practically I need to add setSqlStatementLogger and setSqlExceptionHelper to jdbcService. (or some config option identifying a class used to format SQLs logged by Hibernate). ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:d2b7993 )

5 years, 6 months

1
0
0 / 0

[JIRA] (HSEARCH-3854) Remove the unnecessary generic type parameter for DocumentElement

by Yoann Rodière (JIRA)

5 years, 6 months

1
0
0 / 0

[JIRA] (HHH-13888) Allow custom SQL loggers by subclassing SqlStatementLogger

by Ivan Březina (JIRA)

Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZTQxZjI1ZDVm... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiZTQxZj... ) HHH-13888 ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiZTQxZj... ) Allow custom SQL loggers by subclassing SqlStatementLogger ( https://hibernate.atlassian.net/browse/HHH-13888?atlOrigin=eyJpIjoiZTQxZj... ) Issue Type: Improvement Affects Versions: 5.4.12 Assignee: Unassigned Components: hibernate-core Created: 04/Mar/2020 03:02 AM Priority: Trivial Reporter: Ivan Březina ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e5ec83... ) Logging of slow SQLs from Hibernate is a cool feature, but it would be even better if you added custom loggers. By adding setSqlStatementLogger into JdbcServices. The background: * it is not guaranteed that calling Statement.toString() will return actual SQL statement. For example Oracle's data replay datasource generates instances of proxy for TxnReplayableStatement. This class implements java.sql.Statement interface but toString() returns hexadecimal number. * as a DBA I face situations where I need to correlate customer's action which slow running query. A custom logger can be extended and can also use Thread context to log slow SQL together with applications request id. * Oracle internally identifies SQL by hash string called SQL_ID (last 8 bytes from MD5 checksum). For it is hard to to translate fragments of SQLs logged into SQL_ID. But I can implement custom logger, which can compute and log the same SQL_ID also on application's side. The is a link to sample POC: https://github.com/ibre5041/ucptest/tree/master/standalone-jpa/src/main/java The class * CustomSqlStatementLogger used several reflection steps to get SQL from datatype TxnReplayableStatement. It also contains sample how SQL_ID is computed. * AppHibernate is a sample application which uses Oracle's UCP connection pool and uses reflection to replace instance of SqlStatementLogger with CustomSqlStatementLogger. At the end to logs something like this: SlowQuery: 2582 milliseconds. SQL_ID: 'bd4aqyt8dzfvf' The rest about the query I can find in Oracle's Active session history: {{ SQL> select sql_text from gv$SQL where sql_id = ‘bd4aqyt8dzfvf’; SQL_TEXT select bookentity0_.id as id1_0_0_, bookentity0_.author as author2_0_0_, bookentity0_.name as name3_0_0_ from BOOK bookentity0_ where bookentity0_.id=:1 }} So practically I need to add setSqlStatementLogger and setSqlExceptionHelper to jdbcService. (or some config option identifying a class used to format SQLs logged by Hibernate). ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13888#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:d2b7993 )

5 years, 6 months

1
0
0 / 0

[JIRA] (HSEARCH-3854) Remove the unnecessary generic type parameter for DocumentElement

by Yoann Rodière (JIRA)

5 years, 6 months

1
0
0 / 0

[JIRA] (HSEARCH-3854) Remove the unnecessary generic type parameter for DocumentElement

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiYTJjNTdm... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-3854?atlOrigin=eyJpIjoiYTJ... ) HSEARCH-3854 ( https://hibernate.atlassian.net/browse/HSEARCH-3854?atlOrigin=eyJpIjoiYTJ... ) Remove the unnecessary generic type parameter for DocumentElement ( https://hibernate.atlassian.net/browse/HSEARCH-3854?atlOrigin=eyJpIjoiYTJ... ) Issue Type: Task Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: backend-elasticsearch, backend-lucene, engine, mapper-pojo Created: 04/Mar/2020 01:10 AM Fix Versions: 6.0.0.Beta-backlog-high-priority Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Throughout the codebase, there are many generic type parameters of the form D extends DocumentElement. These parameters are unnecessary, because we always use the base class DocumentElement and never take advantage of methods on subtypes. They make everything more complicated for no good reason: let's remove them. ( https://hibernate.atlassian.net/browse/HSEARCH-3854#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3854#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:d2b7993 )

5 years, 6 months

1
0
0 / 0

[JIRA] (HSEARCH-3842) Expose a global option to use ReindexOnUpdate.NO as a default

by Yoann Rodière (JIRA)

5 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2020