[
https://issues.apache.org/jira/browse/METAMODEL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803193#comment-14803193
]
Kasper Sørensen commented on METAMODEL-189:
-------------------------------------------
Can you be more specific? In terms of your expectations, and what you're trying
to do and what goes wrong?
A gut-reaction to your statement here: Yes MongoDB is schemaless, but MetaModel
isn't. In MongoDB you get to either specify a schema model or let MM detect
one. It might be that this concept doesn't fit all your wishes for a MongoDB
driver, but it goes a long way in terms of making a unified connector that
works the same way on MongoDB as any other datastore.
If this is the issue, I guess we could look at it constructively also. Maybe
MetaModel should have something like a SchemalessTable or UnstructuredTable or
whatever. In such cases I guess we could have a special treatment to not
validate all column paths, but simply pass them on as expressions to the
underlying datastore. The problems with this would be quite clear to me too
though: Loss of safety when querying and non-standard behaviour of these
connectors compared to the rest.
> Metamodel tries to look into mongodb schema before insert or query
> ------------------------------------------------------------------
>
> Key: METAMODEL-189
> URL: https://issues.apache.org/jira/browse/METAMODEL-189
> Project: Apache MetaModel
> Issue Type: Bug
> Reporter: Hosur Narahari
>
> MongoDB is schemaless database but metamodel checks schema before insert or
> query of collections. This causes failure to insert or query data even if it
> is a valid one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
