[
https://issues.apache.org/jira/browse/METAMODEL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022305#comment-15022305
]
Hosur Narahari commented on METAMODEL-189:
------------------------------------------
Sorry for not looking at this for long time. Had been busy some other work.
What I meant is, MongoDB is schema less and you can insert pretty much
anything. And when you try to fetch some column, only those documents(json
objects) with that column gets returned. But since mongodb if not given a
schema try to detect one, which fails for many scenarios. What I think is we
should avoid checking schema for this kind of database. What we are doing is
trying to do is, design schema for schema less database.
Is this inline with development objective of Metamodel?
> 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)
