[JBoss JIRA] (TEIID-2958) MongoDB: Remove the need to have parent id in embedded table
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2958?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2958.
---------------------------------
Fix Version/s: 8.7.1
8.9
Resolution: Done
Removed the need to contain the parent document key in the embedded document, which is duplication. This applies to all MERGE, EMBEDDED scenarios.
TEIID-3040 takes this concept further and removes the need for specifying the values as IDRef
> MongoDB: Remove the need to have parent id in embedded table
> -------------------------------------------------------------
>
> Key: TEIID-2958
> URL: https://issues.jboss.org/browse/TEIID-2958
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: MongoDB with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
> Fix For: 8.7.1, 8.9
>
>
> Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work.
> I am thinking the following case. For example I have a JSON object like this:
> {code}
> Customer
> {
> _id: 1374932,
> FirstName: "John",
> LastName: "Doe",
> Address: {
> _id: 43839430,
> customer_id: IDRef("Customer", 1374932)
> Street: "123 Lane",
> City: "New York",
> State: "NY",
> Zipcode: "12345"
> }
> }
> {code}
> the Teiid should work with document such as
>
> {code}
> Customer
> {
> _id: 1374932,
> FirstName: "John",
> LastName: "Doe",
> Address: {
> _id: 43839430,
> Street: "123 Lane",
> City: "New York",
> State: "NY",
> Zipcode: "12345"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (TEIID-2958) MongoDB: Remove the need to have parent id in embedded table
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2958?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-2958:
--------------------------------
Description:
Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work.
I am thinking the following case. For example I have a JSON object like this:
{code}
Customer
{
_id: 1374932,
FirstName: "John",
LastName: "Doe",
Address: {
_id: 43839430,
customer_id: IDRef("Customer", 1374932)
Street: "123 Lane",
City: "New York",
State: "NY",
Zipcode: "12345"
}
}
{code}
the Teiid should work with document such as
{code}
Customer
{
_id: 1374932,
FirstName: "John",
LastName: "Doe",
Address: {
_id: 43839430,
Street: "123 Lane",
City: "New York",
State: "NY",
Zipcode: "12345"
}
}
{code}
was:
Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work.
I am thinking the following case. For example I have a JSON object like this:
{code}
Customer
{
_id: 1374932,
FirstName: "John",
LastName: "Doe",
Address: {
_id: 43839430,
Street: "123 Lane",
City: "New York",
State: "NY",
Zipcode: "12345"
}
}
{code}
In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema:
{code}
CREATE FOREIGN TABLE Customer (
CustomerId integer PRIMARY KEY,
FirstName varchar(25),
LastName varchar(25),
address__id integer,
address_Street varchar(50),
address_City varchar(25),
address_State varchar(25),
address_Zipcode varchar(6),
) OPTIONS(UPDATABLE 'TRUE');
{code}
> MongoDB: Remove the need to have parent id in embedded table
> -------------------------------------------------------------
>
> Key: TEIID-2958
> URL: https://issues.jboss.org/browse/TEIID-2958
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: MongoDB with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
>
> Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work.
> I am thinking the following case. For example I have a JSON object like this:
> {code}
> Customer
> {
> _id: 1374932,
> FirstName: "John",
> LastName: "Doe",
> Address: {
> _id: 43839430,
> customer_id: IDRef("Customer", 1374932)
> Street: "123 Lane",
> City: "New York",
> State: "NY",
> Zipcode: "12345"
> }
> }
> {code}
> the Teiid should work with document such as
>
> {code}
> Customer
> {
> _id: 1374932,
> FirstName: "John",
> LastName: "Doe",
> Address: {
> _id: 43839430,
> Street: "123 Lane",
> City: "New York",
> State: "NY",
> Zipcode: "12345"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (TEIID-2958) MongoDB: Remove the need to have parent id in embedded table
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2958?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-2958:
--------------------------------
Summary: MongoDB: Remove the need to have parent id in embedded table (was: MongoDB: Put nested JSON documents in one single table)
> MongoDB: Remove the need to have parent id in embedded table
> -------------------------------------------------------------
>
> Key: TEIID-2958
> URL: https://issues.jboss.org/browse/TEIID-2958
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: MongoDB with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
>
> Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work.
> I am thinking the following case. For example I have a JSON object like this:
> {code}
> Customer
> {
> _id: 1374932,
> FirstName: "John",
> LastName: "Doe",
> Address: {
> _id: 43839430,
> Street: "123 Lane",
> City: "New York",
> State: "NY",
> Zipcode: "12345"
> }
> }
> {code}
>
> In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema:
> {code}
> CREATE FOREIGN TABLE Customer (
> CustomerId integer PRIMARY KEY,
> FirstName varchar(25),
> LastName varchar(25),
> address__id integer,
> address_Street varchar(50),
> address_City varchar(25),
> address_State varchar(25),
> address_Zipcode varchar(6),
> ) OPTIONS(UPDATABLE 'TRUE');
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (TEIID-3056) MongoDB: Put nested JSON documents in one single table
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-3056:
-----------------------------------
Summary: MongoDB: Put nested JSON documents in one single table
Key: TEIID-3056
URL: https://issues.jboss.org/browse/TEIID-3056
Project: Teiid
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Misc. Connectors
Affects Versions: 8.7
Environment: MongoDB with Teiid
Reporter: Ivan Chan
Assignee: Ramesh Reddy
Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work.
I am thinking the following case. For example I have a JSON object like this:
{code}
Customer
{
_id: 1374932,
FirstName: "John",
LastName: "Doe",
Address: {
_id: 43839430,
Street: "123 Lane",
City: "New York",
State: "NY",
Zipcode: "12345"
}
}
{code}
In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema:
{code}
CREATE FOREIGN TABLE Customer (
CustomerId integer PRIMARY KEY,
FirstName varchar(25),
LastName varchar(25),
address__id integer,
address_Street varchar(50),
address_City varchar(25),
address_State varchar(25),
address_Zipcode varchar(6),
) OPTIONS(UPDATABLE 'TRUE');
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (TEIID-2958) MongoDB: Put nested JSON documents in one single table
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2958?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-2958:
--------------------------------
Description:
Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work.
I am thinking the following case. For example I have a JSON object like this:
{code}
Customer
{
_id: 1374932,
FirstName: "John",
LastName: "Doe",
Address: {
_id: 43839430,
Street: "123 Lane",
City: "New York",
State: "NY",
Zipcode: "12345"
}
}
{code}
In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema:
{code}
CREATE FOREIGN TABLE Customer (
CustomerId integer PRIMARY KEY,
FirstName varchar(25),
LastName varchar(25),
address__id integer,
address_Street varchar(50),
address_City varchar(25),
address_State varchar(25),
address_Zipcode varchar(6),
) OPTIONS(UPDATABLE 'TRUE');
{code}
was:
Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work.
I am thinking the following case. For example I have a JSON object like this:
Customer
{
_id: 1374932,
FirstName: "John",
LastName: "Doe",
Address:
{
_id: 43839430,
Street: "123 Lane",
City: "New York",
State: "NY",
Zipcode: "12345"
}
}
In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema:
CREATE FOREIGN TABLE Customer (
CustomerId integer PRIMARY KEY,
FirstName varchar(25),
LastName varchar(25),
address__id integer,
address_Street varchar(50),
address_City varchar(25),
address_State varchar(25),
address_Zipcode varchar(6),
) OPTIONS(UPDATABLE 'TRUE');
> MongoDB: Put nested JSON documents in one single table
> -------------------------------------------------------
>
> Key: TEIID-2958
> URL: https://issues.jboss.org/browse/TEIID-2958
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: MongoDB with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
>
> Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work.
> I am thinking the following case. For example I have a JSON object like this:
> {code}
> Customer
> {
> _id: 1374932,
> FirstName: "John",
> LastName: "Doe",
> Address: {
> _id: 43839430,
> Street: "123 Lane",
> City: "New York",
> State: "NY",
> Zipcode: "12345"
> }
> }
> {code}
>
> In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema:
> {code}
> CREATE FOREIGN TABLE Customer (
> CustomerId integer PRIMARY KEY,
> FirstName varchar(25),
> LastName varchar(25),
> address__id integer,
> address_Street varchar(50),
> address_City varchar(25),
> address_State varchar(25),
> address_Zipcode varchar(6),
> ) OPTIONS(UPDATABLE 'TRUE');
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (TEIID-3040) MongoDB: Remove the IDREF fields for the FK fields
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3040?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3040.
---------------------------------
Fix Version/s: 8.7.1
Resolution: Done
Modified translator for necessary changes. The JOIN capabilities can still be used as before. There was no reason to keep extra metadata in terms of using DBRef and added complexity to documents when Teiid already has access to the schema.
> MongoDB: Remove the IDREF fields for the FK fields
> --------------------------------------------------
>
> Key: TEIID-3040
> URL: https://issues.jboss.org/browse/TEIID-3040
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.7.1, 8.9
>
>
> TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
> If the schema looks like
> {code}
> CREATE FOREIGN TABLE Customer (
> id integer PRIMARY KEY,
> firstName string,
> lastName string,
> email_addr string,
> FORIEGN KEY (email_addr) REFERENCES Email(address)
> );
> CREATE FOREIGN TABLE Email (
> address string PRIMARY KEY,
> provider string
> ) OPTIONS ("teiid_mongo:MERGE" 'Customer');
> {code}
> Currently Teiid writes the document as
> {code}
> Customer
> {
> "_id" : 1,
> "firstName" : "Ramesh",
> "lastName" : "Reddy",
> "email_addr" : DBRef("EMail", "abc(a)abc.com"),
> "EMail" : {
> "_id": "abc(a)abc.com",
> "provider" : "Comcast"
> }
> }
> {code}
> change to:
> {code}
> customer
> {
> "_id" : 1,
> "firstName" : "Ramesh",
> "lastName" : "Reddy",
> "email_addr" : "abc(a)abc.com",
> "EMail" : {
> "provider" : "Comcast"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (TEIID-3040) MongoDB: Remove the IDREF fields for the FK fields
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3040?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3040:
--------------------------------
Description:
TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
If the schema looks like
{code}
CREATE FOREIGN TABLE Customer (
id integer PRIMARY KEY,
firstName string,
lastName string,
email_addr string,
FORIEGN KEY (email_addr) REFERENCES Email(address)
);
CREATE FOREIGN TABLE Email (
address string PRIMARY KEY,
provider string
) OPTIONS ("teiid_mongo:MERGE" 'Customer');
{code}
Currently Teiid writes the document as
{code}
Customer
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email_addr" : DBRef("EMail", "abc(a)abc.com"),
"EMail" : {
"_id": "abc(a)abc.com",
"provider" : "Comcast"
}
}
{code}
change to:
{code}
customer
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email_addr" : "abc(a)abc.com",
"EMail" : {
"provider" : "Comcast"
}
}
{code}
was:
TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
If the schema looks like
CREATE FOREIGN TABLE Customer (
id integer PRIMARY KEY,
firstName string,
lastName string,
email_addr string,
FORIEGN KEY (email_addr) REFERENCES Email(address)
);
CREATE FOREIGN TABLE Email (
address string PRIMARY KEY,
provider string
) OPTIONS ("teiid_mongo:MERGE" 'Customer');
Currently Teiid writes the document as
{code}
Customer
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email_addr" : DBRef("EMail", "abc(a)abc.com"),
"EMail" : {
"_id": "abc(a)abc.com",
"provider" : "Comcast"
}
}
{code}
change to:
{code}
customer
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email_addr" : "abc(a)abc.com",
"EMail" : {
"provider" : "Comcast"
}
}
{code}
> MongoDB: Remove the IDREF fields for the FK fields
> --------------------------------------------------
>
> Key: TEIID-3040
> URL: https://issues.jboss.org/browse/TEIID-3040
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.9
>
>
> TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
> If the schema looks like
> {code}
> CREATE FOREIGN TABLE Customer (
> id integer PRIMARY KEY,
> firstName string,
> lastName string,
> email_addr string,
> FORIEGN KEY (email_addr) REFERENCES Email(address)
> );
> CREATE FOREIGN TABLE Email (
> address string PRIMARY KEY,
> provider string
> ) OPTIONS ("teiid_mongo:MERGE" 'Customer');
> {code}
> Currently Teiid writes the document as
> {code}
> Customer
> {
> "_id" : 1,
> "firstName" : "Ramesh",
> "lastName" : "Reddy",
> "email_addr" : DBRef("EMail", "abc(a)abc.com"),
> "EMail" : {
> "_id": "abc(a)abc.com",
> "provider" : "Comcast"
> }
> }
> {code}
> change to:
> {code}
> customer
> {
> "_id" : 1,
> "firstName" : "Ramesh",
> "lastName" : "Reddy",
> "email_addr" : "abc(a)abc.com",
> "EMail" : {
> "provider" : "Comcast"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (TEIID-3040) MongoDB: Remove the IDREF fields for the FK fields
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3040?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3040:
--------------------------------
Description:
TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
If the schema looks like
CREATE FOREIGN TABLE Customer (
id integer PRIMARY KEY,
firstName string,
lastName string,
email_addr string,
FORIEGN KEY (email_addr) REFERENCES Email(address)
);
CREATE FOREIGN TABLE Email (
address string PRIMARY KEY,
provider string
) OPTIONS ("teiid_mongo:MERGE" 'Customer');
Currently Teiid writes the document as
{code}
Customer
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email_addr" : DBRef("EMail", "abc(a)abc.com"),
"EMail" : {
"_id": "abc(a)abc.com",
"provider" : "Comcast"
}
}
{code}
change to:
{code}
customer
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email_addr" : "abc(a)abc.com",
"EMail" : {
"provider" : "Comcast"
}
}
{code}
was:
TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
for ex: Currently we have
{code}
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email" : DBRef("EMail", "abc(a)abc.com"),
"acct_id" : DBRef("Accounts", 1),
"Accounts" : {
"_id": 1,
"Name" : "Wireless"
},
"EMail" : {
"_id": "abc(a)abc.com",
"provider" : "Comcast"
}
}
{code}
change to:
{code}
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email" : "abc(a)abc.com",
"acct_id" : 1,
"Accounts" : {
"Name" : "Wireless"
},
"EMail" : {
"provider" : "Comcast"
}
}
{code}
> MongoDB: Remove the IDREF fields for the FK fields
> --------------------------------------------------
>
> Key: TEIID-3040
> URL: https://issues.jboss.org/browse/TEIID-3040
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.9
>
>
> TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
> If the schema looks like
> CREATE FOREIGN TABLE Customer (
> id integer PRIMARY KEY,
> firstName string,
> lastName string,
> email_addr string,
> FORIEGN KEY (email_addr) REFERENCES Email(address)
> );
> CREATE FOREIGN TABLE Email (
> address string PRIMARY KEY,
> provider string
> ) OPTIONS ("teiid_mongo:MERGE" 'Customer');
> Currently Teiid writes the document as
> {code}
> Customer
> {
> "_id" : 1,
> "firstName" : "Ramesh",
> "lastName" : "Reddy",
> "email_addr" : DBRef("EMail", "abc(a)abc.com"),
> "EMail" : {
> "_id": "abc(a)abc.com",
> "provider" : "Comcast"
> }
> }
> {code}
> change to:
> {code}
> customer
> {
> "_id" : 1,
> "firstName" : "Ramesh",
> "lastName" : "Reddy",
> "email_addr" : "abc(a)abc.com",
> "EMail" : {
> "provider" : "Comcast"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (TEIID-3040) MongoDB: Remove the IDREF fields for the FK fields
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3040?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3040:
--------------------------------
Description:
TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
for ex: Currently we have
{code}
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email" : DBRef("EMail", "abc(a)abc.com"),
"acct_id" : DBRef("Accounts", 1),
"Accounts" : {
"_id": 1,
"Name" : "Wireless"
},
"EMail" : {
"_id": "abc(a)abc.com",
"provider" : "Comcast"
}
}
{code}
change to:
{code}
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email" : "abc(a)abc.com",
"acct_id" : 1,
"Accounts" : {
"Name" : "Wireless"
},
"EMail" : {
"provider" : "Comcast"
}
}
{code}
was:
TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
for ex: Currently we have
{code}
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email" : DBRef("EMail", "abc(a)abc.com"),
"acct_id" : DBRef("Accounts", 1),
"Accounts" : {
"Name" : "Wireless"
},
"EMail" : {
"provider" : "Comcast"
}
}
{code}
change to:
{code}
{
"_id" : 1,
"firstName" : "Ramesh",
"lastName" : "Reddy",
"email" : "abc(a)abc.com",
"acct_id" : 1,
"Accounts" : {
"Name" : "Wireless"
},
"EMail" : {
"provider" : "Comcast"
}
}
{code}
> MongoDB: Remove the IDREF fields for the FK fields
> --------------------------------------------------
>
> Key: TEIID-3040
> URL: https://issues.jboss.org/browse/TEIID-3040
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.9
>
>
> TEIID-2958 has been working towards removing the IDREF fields from embedded documents. I see no reason to represent FK in the parent table with IDREF either. This will make the document model representation simple and aligns with how a typical developer would design.
> for ex: Currently we have
> {code}
> {
> "_id" : 1,
> "firstName" : "Ramesh",
> "lastName" : "Reddy",
> "email" : DBRef("EMail", "abc(a)abc.com"),
> "acct_id" : DBRef("Accounts", 1),
> "Accounts" : {
> "_id": 1,
> "Name" : "Wireless"
> },
> "EMail" : {
> "_id": "abc(a)abc.com",
> "provider" : "Comcast"
> }
> }
> {code}
> change to:
> {code}
> {
> "_id" : 1,
> "firstName" : "Ramesh",
> "lastName" : "Reddy",
> "email" : "abc(a)abc.com",
> "acct_id" : 1,
> "Accounts" : {
> "Name" : "Wireless"
> },
> "EMail" : {
> "provider" : "Comcast"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (TEIID-3055) Querying JDG local cache using greater than value cause exception
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3055?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-3055:
-------------------------------
Fix Version/s: 8.7.1
8.9
Git Pull Request: https://github.com/teiid/teiid/pull/284
> Querying JDG local cache using greater than value cause exception
> -----------------------------------------------------------------
>
> Key: TEIID-3055
> URL: https://issues.jboss.org/browse/TEIID-3055
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7.1, 8.9
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 8.7.1, 8.9
>
>
> Issuing query: select nss, valor_inicial, valor_final from CacheView.Resumen where valor_inicial > 950.0
> produces the following in the query plan:
> USER COMMAND:
> SELECT nss, valor_inicial, valor_final FROM CacheView.Resumen WHERE nss > '950.0'
> request=/1MuNPfoG76j.0.0.5: org.hibernate.search.SearchException: Cannot create numeric range query for field saldo.valorInicial, since values are not numeric (int,long, short or double)
> at org.hibernate.search.bridge.util.impl.NumericFieldUtils.createNumericRangeQuery(NumericFieldUtils.java:69)
> at org.hibernate.search.query.dsl.impl.ConnectedMultiFieldsRangeQueryBuilder.createQuery(ConnectedMultiFieldsRangeQueryBuilder.java:107)
> at org.hibernate.search.query.dsl.impl.ConnectedMultiFieldsRangeQueryBuilder.createQuery(ConnectedMultiFieldsRangeQueryBuilder.java:83)
> at org.teiid.translator.object.infinispan.LuceneSearch.createRangeAboveQuery(LuceneSearch.java:349)
> at org.teiid.translator.object.infinispan.LuceneSearch.visit(LuceneSearch.java:217)
> at org.teiid.translator.object.infinispan.LuceneSearch.buildQueryFromWhereClause(LuceneSearch.java:145)
> at org.teiid.translator.object.infinispan.LuceneSearch.performSearch(LuceneSearch.java:66)
> at org.teiid.translator.object.infinispan.InfinispanExecutionFactory.search(InfinispanExecutionFactory.java:119)
> at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:102)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:312) [te
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months