Open irozzo-1A opened 4 years ago
We're not opposed to an explicit AWS DocumentDB driver. That said, our MongoDB driver is meant to support MongoDB, and we'll be following Mongo's API implementation, not AWS's.
@irozzo-1A if I may ask, how did you add Aws DocumentDB to metabase in the first place? I seem to have difficulties in doing that. What I have done:
Host
(either one has same error)
cluster endpoint: <db-instance-name>.cluster-<someRandomString>.<region>.docdb.amazonaws.com
instance endpoint: <db-instance-name>.<someRandomString>.<region>.docdb.amazonaws.com
Additional Mongo connection string options
ssl=true&ssl_ca_certs=<aws-certs.pem>&retryWrites=false
Authentication Database
Automatically run queries when doing simple filtering and summarizing
Timed out after 3000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=<db-instance-name>.someRandomString.<region>.docdb.amazonaws.com:27017, type=UNKNOWN, state=CONNECTING}]
I have tried both Writer and Reader instance
@purwk I can only get it to work with TLS disabled. Then it works as expected
I opened an issue for requesting an official AWS DocumentDB driver at https://github.com/metabase/metabase/issues/13080, but it was closed and pointed to this as a duplicate.
I guess I'll start the discussion here instead. I am willing to pay and provide access to an AWS DocumentDB instance for anybody willing to put in the development hours to get an official DocumentDB driver working for Metabase. It should be fairly similar to MongoDB, except there are edge cases such as:
Command failed with error 305: 'Aggregation project operator not supported: '$let'' on server xxxyyyzzz.us-east-2.docdb.amazonaws.com:27017. The full response is { "ok" : 0.0, "errmsg" : "Aggregation project operator not supported: '$let'", "code" : 305 }
@purwk In terms of connecting, the following works:
Thanks.
Hi, any news on this issue? Is there any way I can help for resolution? Thanks
There is a workaround that I've been using:
You can then save the question to be able to view the full table without applying the workaround each time.
Hi there,
Are there any updates or a timeline when Metabase will support filtering by dates on AWS DocumentDB? I have seen posts that describes that a new connector needs to be implemented.
I encountered an error when trying to group by date using AWS DocumentDB. I found a possible workaround -- ask ChatGPT to convert a MongoDB query to a DocumentDB query.
I'm seeing this error now Sessions are not supported by the MongoDB cluster to which this client is connected
@manskx we're fixing that in 48.2
I'm still seeing the Sessions are not supported by the MongoDB cluster to which this client is connected
in 49.14
@sra documentdb is not mongo
If anyone needs to connect to DocumentDB and have support from us, you should do it via Athena, as documentdb has diverged too much from Mongo and we will focus only on the latter
I'am trying to use Metabase v0.33.2 with AWS DocumentDB, which implements MongoDB 3.6 API and claims to be compatible with MongoDB drivers with some limitations. I managed to import a DB successfully (apart from #10942), but some features seem not to work correctly e.g. when creating a "Simple question" on some collections I get:
are you aware of someone using metabase with AWS DocumentDB? Do you plan to support it? Thx
similar to #4631?
:arrow_down: Please click the :+1: reaction instead of leaving a
+1
orupdate?
comment