Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HSEARCH-4678 (
https://hibernate.atlassian.net/browse/HSEARCH-4678?atlOrigin=eyJpIjoiNWF...
)
Re: select nextval ('hsearch_outbox_event_generator ') performs very slowly on
CockroachDB,why not use UUID (
https://hibernate.atlassian.net/browse/HSEARCH-4678?atlOrigin=eyJpIjoiNWF...
)
we can use the jpa annotations
That’s not an option, as Hibernate Search needs to be able to add that entity to the
Hibernate ORM mapping conditionally depending on settings.
Believe me, we’re not using XML mapping because we like it 😑 It’s just the only solution
for dynamic mapping (yes, it’s dynamic).
Also, I don’t really want to expose these entity types as API, because that will get in
the way of future evolutions. There’s a middle ground to be found between flexibility for
Hibernate Search users and flexibility for Hibernate Search developers.
You can already change the XML mapping yourself if you want, through configuration
properties. Though that’s completely unsupported and could break at any time: see
org.hibernate.search.mapper.orm.coordination.outboxpolling.cfg.spi.HibernateOrmMapperOutboxPollingSpiSettings#OUTBOXEVENT_ENTITY_MAPPING.
(
https://hibernate.atlassian.net/browse/HSEARCH-4678#add-comment?atlOrigin...
) Add Comment (
https://hibernate.atlassian.net/browse/HSEARCH-4678#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=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100208- sha1:399748d )