Charles
My feedback
141 results found
-
41 votesCharles supported this idea ·
-
4 votesCharles supported this idea ·
-
13 votes
We have a private preview available for this feature. Please enroll in our early access program here ( https://www.mongodb.com/dasal ) if interested or reply to this update.
Charles supported this idea · -
7 votes
An error occurred while saving the comment -
43 votesCharles supported this idea ·
-
50 votesCharles supported this idea ·
-
19 votesCharles supported this idea ·
-
66 votesCharles supported this idea ·
-
19 votesCharles supported this idea ·
-
31 votesCharles supported this idea ·
-
57 votesCharles supported this idea ·
-
32 votesCharles supported this idea ·
-
413 votesCharles supported this idea ·
-
4 votesCharles supported this idea ·
-
4 votesCharles supported this idea ·
-
9 votesCharles supported this idea ·
-
16 votesCharles supported this idea ·
-
49 votes
An error occurred while saving the comment Charles commentedYou can actually do this already if the other resource(s) are XA aware. You just have to prepare on the XA resource(s) (no prepare for Mongo), then commit mongo first and, if successful, commit the XA transaction. So the XA transaction wraps the single non-XA resource between the XA prepare and XA commit.
-
4 votesCharles supported this idea ·
-
139 votesCharles supported this idea ·
Could we create an example of using AWS Glue to move raw data into catalogued S3 buckets then queried with ADL?