June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1741) Record level audit trail in teiid log files

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1741?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1741. --------------------------------- > Record level audit trail in teiid log files > ------------------------------------------- > > Key: TEIID-1741 > URL: https://issues.jboss.org/browse/TEIID-1741 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Reporter: Monika Ahuja > Assignee: Steven Hawkins > Fix For: 8.11 > > > In order to track the audit trail for patient identified information access, we would like to track the executed queries, results as well as the timestamps for each user's query and its result. Essentially we need a report providing the list of Medical Record Numbers accessed by each user id and I think we can use the Logs to track that (unless you suggest a better way). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3358) Issues with entity set names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3358. --------------------------------- > Issues with entity set names > ---------------------------- > > Key: TEIID-3358 > URL: https://issues.jboss.org/browse/TEIID-3358 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1.6_2, 8.11, 8.7.3 > > > The entity set name used for sql generation should be the fully qualified name. If there is for example two table with the same names in schemas visible to odata, but one of the tables does not have a key, then an ambiguous name exception will be thrown if an odata url is used with only the base table name. > It also appears that the URI link in the results metadata uses the non-qualified table name, which will have issues in the scenario above. > We may also need to document or add an additional check for ambiguity as the OData4j findEdmEntitySet logic will return the first matching entity, which is generally against our approach to resolving. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3394) Null values in oidvector and int2vector should be 0

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3394?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3394. --------------------------------- > Null values in oidvector and int2vector should be 0 > --------------------------------------------------- > > Key: TEIID-3394 > URL: https://issues.jboss.org/browse/TEIID-3394 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > If an oid or int2 vector has a null value in it our logic will omit that value, which results in an array out of bounds exception in the pg JDBC client. PostgreSQL will actually substitute 0 for null values. This can occur in querying pg_proc with a procedure that has an array argument. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3474) Inconsistent results of RIGHT function for different datasources

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3474?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3474. --------------------------------- > Inconsistent results of RIGHT function for different datasources > ---------------------------------------------------------------- > > Key: TEIID-3474 > URL: https://issues.jboss.org/browse/TEIID-3474 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Environment: OS: Fedora 20 > arch: x86_64 > java: oracle 1.8 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > The RIGHT function returns different results for different datasources. Some of those results are inconsistent with definition of the RIGHT(x,y) function. > ======= > +*Query: SELECT intkey, RIGHT(intkey, 1) FROM table ORDER BY intkey*+ > *Teradata, SQLServer, Sybase, Ingres, MySQL, Oracle (this result is OK):* > 0 0 > 1 1 > 2 2 > ... > 10 0 > 11 1 > ... > 100 0 > 101 1 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " > ===== > +*Query:SELECT intkey, RIGHT(intkey, 2) FROM table ORDER BY intkey*+ > *SQLServer, Sybase, Ingress, MySQL, Teradata (this result is OK):* > 0 0 > 1 1 > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Oracle:* > 0 <null> > 1 <null> > 2 <null> > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3450) bulk values are set directly from client

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3450?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3450. --------------------------------- > bulk values are set directly from client > ---------------------------------------- > > Key: TEIID-3450 > URL: https://issues.jboss.org/browse/TEIID-3450 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.10.1, 8.11 > > > Using a prepared bulk query, such as "insert ... values (?, ...)" that is passed to the source, the bound values are coming directly from the client rather than being the resolved form - which will be the correct runtime object and type. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3451) OData does not inject schema into queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3451?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3451. --------------------------------- > OData does not inject schema into queries > ----------------------------------------- > > Key: TEIID-3451 > URL: https://issues.jboss.org/browse/TEIID-3451 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11, 8.7.3 > > > OData service does not inject a fully qualified object names for tables for POSTS, PUTs, and DELETEs: > 12:50:34,367 DEBUG [org.teiid.COMMAND_LOG] (http-localhost/127.0.0.1:8080-1) START USER COMMAND: startTime=2015-04-22 12:50:34.367 requestID=XxHTbednhDq7.0 txID=null sessionID=XxHTbednhDq7 applicationName=JDBC principal=teiidUser@teiid-security vdbName=ImsOne vdbVersion=2 sql=INSERT INTO Subscription (SUBSCRIPTION_ID, CLIENT_NAME, DEST_CONNECTION_URI, DEST_SCHEMA_NAME, DEST_TABLE_NAME, PROVIDER_URL, TOPIC_NAME) VALUES (?, ?, ?, ?, ?, ?, ?) > 12:50:34,380 DEBUG [org.teiid.COMMAND_LOG] (http-localhost/127.0.0.1:8080-1) ERROR USER COMMAND: endTime=2015-04-22 12:50:34.379 requestID=XxHTbednhDq7.0 txID=null sessionID=XxHTbednhDq7 principal=teiidUser@teiid-security vdbName=ImsOne vdbVersion=2 finalRowCount=null > 12:50:34,380 WARN [org.teiid.PROCESSOR] (http-localhost/127.0.0.1:8080-1) TEIID30020 Processing exception for request XxHTbednhDq7.0 'Group specified is ambiguous, resubmit the query by fully qualifying the group name: Subscription'. Originally QueryResolverException ResolverUtil.java:814. Enable more detailed logging to see the entire stacktrace. > 12:50:34,383 WARN [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-1) TEIID16012 Could not produce a successful OData response. Returning status ServerErrorException with message Group specified is ambiguous, resubmit the query by fully qualifying the group name: Subscription. > Same insert works fine over JDBC. Offending line from 8.7.0 public github: > https://github.com/teiid/teiid/blob/8.7.x/odata/src/main/java/org/teiid/o... > Note that private Table findTable() on line 925 depends upon org.odata4j.core.EdmEntitySet#getName to return the name, but this is not fully qualified -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3443) wrong estimation of BufferFrontedFileStoreCache.maxMemoryBlocks

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3443?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3443. --------------------------------- > wrong estimation of BufferFrontedFileStoreCache.maxMemoryBlocks > --------------------------------------------------------------- > > Key: TEIID-3443 > URL: https://issues.jboss.org/browse/TEIID-3443 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4, 8.10 > Environment: JDV 6.0.x, 6.1.0 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > BufferFrontedFileStoreCache.maxMemoryBlocks is under-estimated. For example, when max-storage-object-size=8000000, maxMemoryBlocks > is 488 at the line #575 in org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize() (after that, it is decrimented some times, but it does not matter). > {code} > main[1] run > > > Breakpoint hit: "thread=MSC service thread 1-3", org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize(), line=573 bci=163 > 573 maxMemoryBlocks = Math.min(maxMemoryBlocks, maxStorageObjectSize>>LOG_BLOCK_SIZE + ((maxStorageObjectSize&BufferFrontedFileStoreCache.BLOCK_MASK)>0?1:0)); > MSC service thread 1-3[1] next > > > Step completed: "thread=MSC service thread 1-3", org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize(), line=575 bci=198 > 575 cleaningThreshold = Math.min(maxMemoryBlocks<<4, blocks>>1); > MSC service thread 1-3[1] dump this > this = { > ...snip... > maxStorageObjectSize: 8000000 > ...snip... > maxMemoryBlocks: 488 > {code} > An actual cache object size for maxMemoryBlocks: 488 is roughly:- > {code} > 8192 * 488 = 3997696 > {code} > It is less than half of maxStorageObjectSize. It sometimes causes TEIID30001. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3471. ----------------------------------- Resolution: Done > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.7.1.6_2, 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-3471: ----------------------------------- > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.7.1.6_2, 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3550) Missing status of VDB in jboss-cli console

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3550?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3550. ----------------------------------- Fix Version/s: 8.12 Resolution: Done Corrected the message. > Missing status of VDB in jboss-cli console > ------------------------------------------ > > Key: TEIID-3550 > URL: https://issues.jboss.org/browse/TEIID-3550 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 8.12 > > > There is missing status in failure description of command "get-vdb". > "failure-description" => "TEIID50096 VDB xyz.1 is {2} and not ACTIVE. " -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015