[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:
--------------------------------
Fix Version/s: 8.9
> 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: Steven Hawkins
> 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" : {
> "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}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 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 reassigned TEIID-3040:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> 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" : {
> "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}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3040) MongoDB: Remove the IDREF fields for the FK fields
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-3040:
-----------------------------------
Summary: 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: Steven Hawkins
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}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3038) Add spatial query support to the Teiid MongoDB translator
by Michael Farwell (JIRA)
[ https://issues.jboss.org/browse/TEIID-3038?page=com.atlassian.jira.plugin... ]
Michael Farwell updated TEIID-3038:
-----------------------------------
Description: We'd like to be able to issue geoIntersects and geoWithin queries through the MongoDB translator. See comment below on a proposed approach.
> Add spatial query support to the Teiid MongoDB translator
> ---------------------------------------------------------
>
> Key: TEIID-3038
> URL: https://issues.jboss.org/browse/TEIID-3038
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.8
> Reporter: Michael Farwell
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> We'd like to be able to issue geoIntersects and geoWithin queries through the MongoDB translator. See comment below on a proposed approach.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3032) Database Logging: Problems with Microsoft
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3032?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3032.
---------------------------------
> Database Logging: Problems with Microsoft
> -----------------------------------------
>
> Key: TEIID-3032
> URL: https://issues.jboss.org/browse/TEIID-3032
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 8.7.1
>
>
> Installed the teiid extension: database logging, and seeing the following errors:
> 14:46:55,588 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB Logging.1 model "LoggingData" metadata failed to load. Reason:TEIID60013 Duplicate Table check_constraints
> 14:46:55,844 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000227: Running hbm2ddl schema export
> 14:46:56,119 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table auditlog
> 14:46:56,120 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'auditlog', because it does not exist or you do not have permission.
> 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table commandlog
> 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'commandlog', because it does not exist or you do not have permission.
> 14:46:56,857 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: create table commandlog (id bigint identity not null, applicationname varchar(255), executionid varchar(50), modelname varchar(255), plan varbinary(MAX), principal varchar(50), requestid varchar(50), rowcount int, sessionid varchar(50), sourcecommand bit, sourcerequestid bigint, sqlcmd varchar(MAX), eventtype varchar(10), logtime datetime2, transactionid varchar(100), translatorname varchar(50), vdbname varchar(255), vdbversion int, primary key (id))
> 14:46:56,858 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Incorrect syntax near the keyword 'plan'.
> 14:46:56,858 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000230: Schema export complete
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3026) NPE using Excel translator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3026?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3026.
---------------------------------
> NPE using Excel translator
> --------------------------
>
> Key: TEIID-3026
> URL: https://issues.jboss.org/browse/TEIID-3026
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.8, 8.7.1
>
>
> {code}
> 10:48:26,620 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException
> at org.teiid.translator.excel.ExcelMetadataProcessor.addTable(ExcelMetadataProcessor.java:106)
> at org.teiid.translator.excel.ExcelMetadataProcessor.process(ExcelMetadataP
> rocessor.java:87)
> at org.teiid.translator.excel.ExcelMetadataProcessor.process(ExcelMetadataProcessor.java:45)
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:915) [teiid-api-8.7.0.Final.jar:8.7.0.Final]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.0.Final.jar:8.7.0.Final]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.0.Final.jar:8.7.0.Final]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.0.Final.jar:8.7.0.Final]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.0.Final.jar:8.7.0.Final]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3025) Issues with sorting by a subquery
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3025?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3025.
---------------------------------
> Issues with sorting by a subquery
> ---------------------------------
>
> Key: TEIID-3025
> URL: https://issues.jboss.org/browse/TEIID-3025
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1
>
>
> We have issues with processing subqueries in the order by clause (either directly through an unrelated column, or indirectly through the select clause). The pushdown processing can fail with an AssertionError during with the languagebridgefactory, while the engine processing can fail with a NPE during the evaluation rewrite.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months