How to debug JPA CriteriaBuilder queries - java

How can I debug a query built with JPA 2.0 CriteriaBuilder? Is there a way to print out the query that is being executed?
I am developing a web application using NetBeans, MySql, GlassFish. I would avoid starting MySql in debug mode, because it is used also for other applications. JPA provider is EclipseLink.

The same attributes in persistence.xml that also print the SQL that is generated from regular JPQL queries, should also print the SQL that is generated from Criteria queries.
E.g.
For Hibernate (used by e.g. JBoss AS) it's:
<property name="hibernate.show_sql" value="true" />
For EclipseLink (used by e.g. GlassFish) it's:
<property name="eclipselink.logging.level" value="FINE"/>
<property name="eclipselink.logging.parameters" value="true"/>
Also see: How to view the SQL queries issued by JPA?

If you are using Java and Spring, under resources, you can adjust your application.properties file and add the line below:
spring.jpa.show-sql=true

Related

hibernate search configuration

Im using hibernate search and elastic search as backend . When i config hibernate and hibernatesearch in xml file everything is ok but whene i config it in java class this warning occur and nothing found in my search .
xml config is:
<properties>
<property name="hibernate.connection.url" value="jdbc:mysql://localhost:3399/elastic" />
<property name="hibernate.connection.username" value="admin" />
<property name="hibernate.connection.password" value="admin" />
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.search.default.indexmanager" value="elasticsearch"/>
<property name="hibernate.search.default.elasticsearch.host" value="http://127.0.0.1:9400"/>
<property name="hibernate.search.default.elasticsearch.index_schema_management_strategy" value="CREATE"/>
<property name="hibernate.search.default.elasticsearch.required_index_status" value="YELLOW"/>
</properties>
java class config is :
java.util.Properties settings = new java.util.Properties();
settings.put(org.hibernate.cfg.Environment.DRIVER, "com.mysql.cj.jdbc.Driver");
settings.put(org.hibernate.cfg.Environment.URL, "jdbc:mysql://127.0.0.1:3399/elastic");
settings.put(org.hibernate.cfg.Environment.USER, "admin");
settings.put(org.hibernate.cfg.Environment.PASS, "admin");
settings.put(org.hibernate.cfg.Environment.DIALECT,"org.hibernate.dialect.MySQL8Dialect");
settings.put(org.hibernate.cfg.Environment.SHOW_SQL, "true");
settings.put(org.hibernate.cfg.Environment.CURRENT_SESSION_CONTEXT_CLASS, "thread");
settings.put(org.hibernate.cfg.Environment.POOL_SIZE, "5");
settings.put("hibernate.search.default.indexmanager", "elasticsearch");
settings.put("hibernate.search.default.elasticsearch.host", "http://127.0.0.1:9400");
settings.put("hibernate.search.default.elasticsearch.index_schema_management_strategy", "CREATE");
settings.put("hibernate.search.default.elasticsearch.required_index_status", "YELLOW");
Warning is :
WARNING: request [HEAD http://127.0.0.1:9400/com.radar.elasticsearch.videogame] returned 1 warnings: [299 Elasticsearch-6.8.0-65b6179 "[types removal] The parameter include_type_name should be explicitly specified in get indices requests to prepare for 7.0. In 7.0 include_type_name will default to 'false', which means responses will omit the type name in mapping definitions."]
You are using Elasticsearch 6.8 where types are deprecated. Please refer removal of types for more info,
You need to pass _doc instead of type name otherwise use include_type_name if you are using your own type name in all the API.
Please refer this official blog for more info
If you plan to upgrade without downtime in a rolling fashion, you
should upgrade to 6.8 first, which is the only 6.x release to have
some features like support for the include_type_name parameter, which
is required to upgrade to 7.0 smoothly.
Elasticsearch support in Hibernate Search 5 is experimental and was only tested with Elasticsearch up to version 5.6.
If you need to upgrade to Elasticsearch 7, upgrade to Hibernate Search 6.
Hibernate Search 6 is currently in Beta but offers revamped APIs that will be a much better fit for Elasticsearch.
It also offers new features not found in Hibernate Search 5, such as support for nested documents or the ability to inject JSON directly into your query (to take advantage of more exotic predicates/sorts/etc. not yet supported by the Hibernate Search DSL).
EDIT: Also, you can find information about the compatibility of Hibernate Search with various other components on this page of the official website.

Hibernate equivalent properties for these openjpa propertie

I have an requirement to use Hibernate Persistence instead of OpenJPA Persistence
I searched in google but didn't get information still looking on it.Any body help on this. I am not much expert in Hibernate.
<property name="openjpa.TransactionMode" value="managed"/>
<property name="openjpa.ConnectionRetainMode" value="always"/>

How create the database through Hibernate

In my spring project, i am using Hibernate to export my entity classes to a previously created database. But this will require the final user knows how to create a database in the Database manager system (Currently I am using Postgresql).
Is there any way of, given only the machine where the postgresql is installed (and the username and password, which is provided when the application is runned the first time), the Hibernate create a new database in the server if it doesn't exist?
If your configuration looks like this
<hibernate-configuration>
<session-factory>
<property name="dialect">org.hibernate.dialect.PostgreSQLDialect</property>
<property name="connection.driver_class">org.postgresql.Driver</property>
<property name="connection.url">jdbc:postgresql://host:port/database</property>
<property name="connection.username">username</property>
<property name="connection.password">password</property>
<property name="current_session_context_class">thread</property>
<property name="hibernate.show_sql">false</property>
<property name="hbm2ddl.auto">update</property>
</session-factory>
</hibernate-configuration>
Then the database will be created by Hibernate automatically.
Update:
Ok now I understand what you want. You want to start the Postgresql server with Hibernate. This is not possible. Hibernate does not do this.
You can do this with
Another script that starts with your application
A maven/ant target.
A build job
But the best solution is to use an in-memory database that does not need an external server (for example H2, or Java derby)
See also
Simulate CREATE DATABASE IF NOT EXISTS for PostgreSQL?
and
Postgres database create if not exists
Take a look of paramater hibernate.hbm2ddl.auto for your hibernate.cfg.xml file. I suggest you this link: Hibernate hbm2ddl.auto, possible values and what they do - any official explanation?
Run "CREATE DATABASE ..." (see http://www.postgresql.org/docs/9.0/static/sql-createdatabase.html) as a native SQL query ...
.createSQLQuery(" ... ").executeUpdate(); ...
Hibernate will - at least as far as I know - not create the database, only the tables in it.
I suppose you need to connect to postgresql via a second persistence unit/connection, because of the chicken-and-egg nature of this approach.

java hibernate query.list returns empty list

I am using hibernate with JPA annotations and Jboss transaction manager I build the session factory open up a session and create a query when i use query.list it always returns me an empty list
any idea?
Few suggestions:
Enable configuration parameter show-sql in persistence.xml. Try this, i.e.
<property name="hibernate.show.sql" value="true" />
Furthermore, it is better to format that using,
<property name="hibernate.format_sql" value="true" />
And then try to run the same query in some SQL Client.
If you are adding values in the database from the command prompt manually, perform the commit operation after insertion. especially in oracle DB

how to configure cache in hibernate with jboss? ? And test as well in kumud console?

Does any one know, how to configure cache for hibernate with jboss ?
My clear question is I am using JPA and Jboss. Every time I call JPA method its creating entity and binding query.
My persistence properties are
<property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/>
<property name="hibernate.cache.provider_class" value="net.sf.ehcache.hibernate.SingletonEhCacheProvider"/>
<property name="hibernate.cache.use_second_level_cache" value="true"/>
<property name="hibernate.cache.use_query_cache" value="true"/>
And I am creating entity manager the way shown below:
emf = Persistence.createEntityManagerFactory("pu");
em = emf.createEntityManager();
em = Persistence.createEntityManagerFactory("pu")
.createEntityManager();
Is there any nice way to manage entity manager resource insted create new every time or any property can set in persistance. Remember it's JPA.
The question is not clear, there are many second level cache providers for Hibernate and they are not application server specific.
To enable the second level cache, you need to set the following properties in Hibernate configuration file hibernate.cfg.xml:
<property name="hibernate.cache.use_second_level_cache">true</property>
And if you want to also enable query result caching:
<property name="hibernate.cache.use_query_cache">true</property>
Then, declare the name of a class that implements org.hibernate.cache.CacheProvider - a cache provider - under the hibernate.cache.provider_class property. For example, to use JBoss Cache 2:
<property name="hibernate.cache.provider_class">org.hibernate.cache.jbc2.JBossCacheRegionFactory</property>
Of course, the JAR for the provider must be added to the application classpath.
That's for the Hibernate side. Depending on the chosen cache provider, there might be additional configuration steps. But as I said, there are many second level cache providers: EHCache, JBoss Cache, Infinispan, Hazelcast, Coherence, GigaSpace, etc.

Categories

Resources