rt any non XA
> datasource
> >in an XA transaction?
> >
> It marks the non-XA datasource as the Last Resource which is committed in
> the last one, so if it fails, rollback all of the other XA datasources.
>
> >- When you said above that Athena is OK did you m
last one, so if it fails, rollback all of the other XA datasources.
>- When you said above that Athena is OK did you mean OK using our
>current CData JDBC driver? Or do we have to use the Camel AWS Athena
> SDK
>to get the behavior you stated?
>
Yeah, using the CData JD
does Quarkus JTA transaction manager support any non XA datasource
in an XA transaction?
- When you said above that Athena is OK did you mean OK using our
current CData JDBC driver? Or do we have to use the Camel AWS Athena SDK
to get the behavior you stated?
- What are the pros/cons
OK, I see. So you are using PG and MongoDB and Ahtena in one service, but I
think only PG supports the XA transaction currently.
And yeah, Quarkus JTA transaction manager only supports using one non-XA
datasource in a XA transaction.
PG + MongoDB is OK
PG + Athena is OK
PG + MongoDB + Athena is no
Hi,
Yes we actually have 4 datasources.
This is the main one, always exists.
db-kind: postgresql
emrDS:
db-kind: other
jdbc:
driver: com.facebook.presto.jdbc.PrestoDriver
dialect: Derby
athenaDS:
db-kind: other
jdbc:
driver: cdata.jdbc.amazonathena.AmazonAthenaDriver
dialect:
Hi David,
Can you describe more about your scenario? Do you want to run Athean and
other data sources in an XA transaction? What transaction manager did you
use, is it quarkus-narayana-jta?
On Wed, Nov 20, 2024 at 7:19 AM David Hoffer wrote:
> https://camel.apache.org/components/4.8.x/aws2-athe
https://camel.apache.org/components/4.8.x/aws2-athena-component.html
We use multiple data sources in our Quarkus application and Athena is one
of them. Is there a way to make this XA compliant? The latest Quarkus is
failing with our current CData driver as its not XA, so looking for
something th
