-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mongodb select * on view returns error CommandNotSupportedOnView #7491
Comments
Could you share the steps to reproduce? Also, you can ask question in the community Slack https://trino.io/slack.html |
there are no specific steps, I tested with both dbeaver and quix; In the catalog the mongodb database and the collection are shown; when doing |
Looks like this is the internal query which is failing:
A naive |
Please share the full stacktrace from webui, Trino and MongoDB version and commands to create a enrichedSites view. |
OK, since I cannot share my data I used sample data to reproduce the error. I'm using MongoDB 4.2.7 Community Go to https://github.com/SouthbankSoftware/dbkoda-data and Download as zip use the latest MongoDB Compass (Version 1.26.1-beta.6 (1.26.1-beta.6)) to add the following mongodb view:
3 click on the drop down arrow next to the green save button and choose create view, name it 'lookupCustomer' Now you have a 'lookupCustomer' View, and it appears in Compass on the left side with the other OrdersExample collections. By clicking on Now go to i.e dbeaver and see the error: As you can see Im using the newest trino version: 354 query:
stacktrace:
|
PS my catalog settings are:
|
OK I was able to find out via mongodb logging what is actually causing the error:
the mongodb connector is doing a |
And the corresponding Line in the connector is trino/plugin/trino-mongodb/src/main/java/io/trino/plugin/mongodb/MongoSession.java Line 266 in 0c58b3d
so maybe a try catch for this case could be enough... |
As far as I checked, the cause is case sensitivity and it should be captured in |
@ebyhr just one more hint: |
It's expected behavior.
Do you mean this issue happens with lowercase? If so, can you share the steps to reproduce? |
OK I tested again without setting
I think now that this is all expected behaviour and I understand now how it works... |
Any Idea why a select * on a mongodb view results in this error:
Thanks
Ognian
The text was updated successfully, but these errors were encountered: