October 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4050) database logging doesn't add command and audit loggers for domain mode

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4050?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4050: ---------------------------------- Fix Version/s: 8.12.5 (was: 8.12.x) > database logging doesn't add command and audit loggers for domain mode > ---------------------------------------------------------------------- > > Key: TEIID-4050 > URL: https://issues.jboss.org/browse/TEIID-4050 > Project: Teiid > Issue Type: Bug > Components: Tooling > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 9.0, 8.12.5 > > > When installing database logging, than no org.teiid.COMMAND_LOG or org.teiid.AUDIT_LOG category loggers are present in domain.xml for ha and full-ha profile. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4050) database logging doesn't add command and audit loggers for domain mode

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4050?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4050. --------------------------------- Resolution: Done > database logging doesn't add command and audit loggers for domain mode > ---------------------------------------------------------------------- > > Key: TEIID-4050 > URL: https://issues.jboss.org/browse/TEIID-4050 > Project: Teiid > Issue Type: Bug > Components: Tooling > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 8.12.5, 9.0 > > > When installing database logging, than no org.teiid.COMMAND_LOG or org.teiid.AUDIT_LOG category loggers are present in domain.xml for ha and full-ha profile. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3810) Updating teiid-tools archetypes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3810?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-3810: ----------------------------------- > Updating teiid-tools archetypes > -------------------------------- > > Key: TEIID-3810 > URL: https://issues.jboss.org/browse/TEIID-3810 > Project: Teiid > Issue Type: Task > Components: Tools > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.5 > > > Updating teiid-tools archetypes to be based on Teiid 8.12.0.Final > Adding in a docs section to be included with the jboss-as7 distribution. > Adding a default ResourceAdapter for the connector. > Adding an example ExecutionFactory unit test that provides a starting point. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3810) Updating teiid-tools archetypes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3810?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3810: ---------------------------------- Fix Version/s: 8.12.5 (was: 8.12.x) > Updating teiid-tools archetypes > -------------------------------- > > Key: TEIID-3810 > URL: https://issues.jboss.org/browse/TEIID-3810 > Project: Teiid > Issue Type: Task > Components: Tools > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.5 > > > Updating teiid-tools archetypes to be based on Teiid 8.12.0.Final > Adding in a docs section to be included with the jboss-as7 distribution. > Adding a default ResourceAdapter for the connector. > Adding an example ExecutionFactory unit test that provides a starting point. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4029) After terminating long running queries remains CPU load > 100% on JBoss java process

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4029?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4029: ---------------------------------- Fix Version/s: (was: 8.12.x) > After terminating long running queries remains CPU load > 100% on JBoss java process > ------------------------------------------------------------------------------------ > > Key: TEIID-4029 > URL: https://issues.jboss.org/browse/TEIID-4029 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.4 > Reporter: Colin Mondesir > Assignee: Steven Hawkins > Attachments: Archive.zip, Case01593403.java, heap.1, heap.2, heap.3, heap.4, heap.5, highcpu-vdb.xml > > > Once the request is submitted the CPU% load on the server remains > 100% despite cancelling the request and terminating the session. The only way I have found to bring the %CPU back to "normal" is to re-start the JDV instance. > 1. Created two files file1.csv (1M rows) and file2.csv (1M rows) > 2. Created two source and view models and VDB > SQL statement is a carthesion product > 3. Deploy VDB > 4. select * from combinedcsv from SQL scrapbook on cancelLongRunningQueries VDB > 5. Goto admin console > 6. Go to the cancelLongRunningQueries VDB > 7. Goto tab Requests and select Terminate > 8. Goto tab Sessions and select Terminate JDBC session > 9. CPU% load on JBoss java process remains > 100% -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4029) After terminating long running queries remains CPU load > 100% on JBoss java process

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4029?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4029. --------------------------------- Resolution: Done > After terminating long running queries remains CPU load > 100% on JBoss java process > ------------------------------------------------------------------------------------ > > Key: TEIID-4029 > URL: https://issues.jboss.org/browse/TEIID-4029 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.4 > Reporter: Colin Mondesir > Assignee: Steven Hawkins > Attachments: Archive.zip, Case01593403.java, heap.1, heap.2, heap.3, heap.4, heap.5, highcpu-vdb.xml > > > Once the request is submitted the CPU% load on the server remains > 100% despite cancelling the request and terminating the session. The only way I have found to bring the %CPU back to "normal" is to re-start the JDV instance. > 1. Created two files file1.csv (1M rows) and file2.csv (1M rows) > 2. Created two source and view models and VDB > SQL statement is a carthesion product > 3. Deploy VDB > 4. select * from combinedcsv from SQL scrapbook on cancelLongRunningQueries VDB > 5. Goto admin console > 6. Go to the cancelLongRunningQueries VDB > 7. Goto tab Requests and select Terminate > 8. Goto tab Sessions and select Terminate JDBC session > 9. CPU% load on JBoss java process remains > 100% -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4029) After terminating long running queries remains CPU load > 100% on JBoss java process

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4029?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-4029: ----------------------------------- > After terminating long running queries remains CPU load > 100% on JBoss java process > ------------------------------------------------------------------------------------ > > Key: TEIID-4029 > URL: https://issues.jboss.org/browse/TEIID-4029 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.4 > Reporter: Colin Mondesir > Assignee: Steven Hawkins > Attachments: Archive.zip, Case01593403.java, heap.1, heap.2, heap.3, heap.4, heap.5, highcpu-vdb.xml > > > Once the request is submitted the CPU% load on the server remains > 100% despite cancelling the request and terminating the session. The only way I have found to bring the %CPU back to "normal" is to re-start the JDV instance. > 1. Created two files file1.csv (1M rows) and file2.csv (1M rows) > 2. Created two source and view models and VDB > SQL statement is a carthesion product > 3. Deploy VDB > 4. select * from combinedcsv from SQL scrapbook on cancelLongRunningQueries VDB > 5. Goto admin console > 6. Go to the cancelLongRunningQueries VDB > 7. Goto tab Requests and select Terminate > 8. Goto tab Sessions and select Terminate JDBC session > 9. CPU% load on JBoss java process remains > 100% -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4492) When using annotations, add option that specifies all child classes to register as part of the JDG schema

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4492?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4492: --------------------------------------- This doesn't appear to be in 8.12.6.6_3? Do you mean that it will be targeted to 8.12.7.6_3? Normally John will update the issue once the commit has been made. > When using annotations, add option that specifies all child classes to register as part of the JDG schema > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-4492 > URL: https://issues.jboss.org/browse/TEIID-4492 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.2, 8.12.6.6_3 > > Attachments: jdg-remote-cache-pojos.jar, jdg-remote-cache-vdb.xml, standalone.xml > > > When using protobuf annotations, need to specify all the child related (e.g, 1-to-1 relationship or 1-to-many relationship) pojo's that also need to be registered with the JDG schema. When these are registered, JDG will auto generate the .proto file and marshallers used by the schema. Which is the information used by the hot rod translator to create the source models. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4271: ---------------------------------- Fix Version/s: (was: 8.12.x) > Consume Teiid OData from Salesforce > ----------------------------------- > > Key: TEIID-4271 > URL: https://issues.jboss.org/browse/TEIID-4271 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steven Hawkins > Assignee: Johnathon Lee > Fix For: 8.12.6.6_3 > > > At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume. > Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-4271. --------------------------------- Resolution: Done > Consume Teiid OData from Salesforce > ----------------------------------- > > Key: TEIID-4271 > URL: https://issues.jboss.org/browse/TEIID-4271 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steven Hawkins > Assignee: Johnathon Lee > Fix For: 8.12.6.6_3 > > > At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume. > Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2016