March 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2840) More control over TTL Snapshot Refresh

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2840?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2840. ----------------------------------- Resolution: Done Rather than introduce additional hint or table metadata, modified the notion of ttl to be invalidating by default - which seems to match better with user expectations. To keep the old behavior of lazy invalidation, a vdb property lazy-invalidation=true can be set. Added a release note to cover this change. > More control over TTL Snapshot Refresh > --------------------------------------- > > Key: TEIID-2840 > URL: https://issues.jboss.org/browse/TEIID-2840 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.7 > > > The ttl load to may need to be changed to a blocking load or some configuration options provided to prevent stale reads after a certain time limit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2786: ---------------------------------- Fix Version/s: 8.7.1 (was: 8.7) Moving to 8.7.1 to revalidate against the next set of changes in Modeshape. > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7.1 > > Attachments: mode.patch > > > When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception: > 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656) > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107) > 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml") > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444) > 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2888) Support .INDEX file VDB loading with Embedded environments

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2888?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2888. ----------------------------------- Resolution: Done Added .index support - at least for vdbs that use separate .index files per schema (roughly Designer 7+) as the .index per type requires a level of load coordination not supported by embedded. Also updated the embedded guide. > Support .INDEX file VDB loading with Embedded environments > ---------------------------------------------------------- > > Key: TEIID-2888 > URL: https://issues.jboss.org/browse/TEIID-2888 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.7 > > > Currently embedded Teiid supports .vdb files, but it does not include the necessary JAR files in the kit to load the .INDEX files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-994) Unable to execute Oracle pipelined table function as procedure

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-994?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-994: --------------------------------- Fix Version/s: 8.7.1 (was: 8.7) Putting in 8.7.1 to see if there is anything else that needs done here from a customer perspective. > Unable to execute Oracle pipelined table function as procedure > -------------------------------------------------------------- > > Key: TEIID-994 > URL: https://issues.jboss.org/browse/TEIID-994 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, Open To Community > > > Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db. > Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2880) Add login username to source query comment, also session and request Id

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2880?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2880. ----------------------------------- Resolution: Done Added the JDBC translator property CommentFormat to set the MessageFormat string for the comment. Updated https://docs.jboss.org/author/display/TEIID/JDBC+Translator with the possible positional properties. > Add login username to source query comment, also session and request Id > ----------------------------------------------------------------------- > > Key: TEIID-2880 > URL: https://issues.jboss.org/browse/TEIID-2880 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Rick Wagner > Assignee: Steven Hawkins > Fix For: 8.7 > > > The user occasionally has problematic queries and while they can go through the command logs to find some details sometimes under heavy usage the logs are rotated at such a rate that they lose the information. > Please add the login id, session Id, and request Id to the source query comment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2880) Add login username to source query comment, also session and request Id

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2880?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2880: --------------------------------------- Yes, I don't see anything that fits neatly, so I'll just code it up using positional parameters and MessageFormat. Then users will at least have a choice of a greater number of variables and format. > Add login username to source query comment, also session and request Id > ----------------------------------------------------------------------- > > Key: TEIID-2880 > URL: https://issues.jboss.org/browse/TEIID-2880 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Rick Wagner > Assignee: Steven Hawkins > Fix For: 8.7 > > > The user occasionally has problematic queries and while they can go through the command logs to find some details sometimes under heavy usage the logs are rotated at such a rate that they lose the information. > Please add the login id, session Id, and request Id to the source query comment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2880) Add login username to source query comment, also session and request Id

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2880?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2880: ------------------------------------- Ok, what I remember from previous usage of String Template in materialization scripts bought in lot of dependencies. > Add login username to source query comment, also session and request Id > ----------------------------------------------------------------------- > > Key: TEIID-2880 > URL: https://issues.jboss.org/browse/TEIID-2880 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Rick Wagner > Assignee: Steven Hawkins > Fix For: 8.7 > > > The user occasionally has problematic queries and while they can go through the command logs to find some details sometimes under heavy usage the logs are rotated at such a rate that they lose the information. > Please add the login id, session Id, and request Id to the source query comment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2888) Support .INDEX file VDB loading with Embedded environments

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2888?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2888: ---------------------------------- Fix Version/s: 8.7 > Support .INDEX file VDB loading with Embedded environments > ---------------------------------------------------------- > > Key: TEIID-2888 > URL: https://issues.jboss.org/browse/TEIID-2888 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.7 > > > Currently embedded Teiid supports .vdb files, but it does not include the necessary JAR files in the kit to load the .INDEX files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2880) Add login username to source query comment, also session and request Id

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2880?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2880: --------------------------------------- The built-in logic uses connection id, request id, and the part identifier. So we do in fact have the session and request id. But not the username. So rather than just putting the username in the existing comment, I'm saying that we can turn this into a translator property. We can either use a simple message format and define positional arguments or we can use a templating approach such as ST4 that can access bean properties to future proof the solution. > Add login username to source query comment, also session and request Id > ----------------------------------------------------------------------- > > Key: TEIID-2880 > URL: https://issues.jboss.org/browse/TEIID-2880 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Rick Wagner > Assignee: Steven Hawkins > Fix For: 8.7 > > > The user occasionally has problematic queries and while they can go through the command logs to find some details sometimes under heavy usage the logs are rotated at such a rate that they lose the information. > Please add the login id, session Id, and request Id to the source query comment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2896) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2896?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2896. ----------------------------------- Resolution: Done Modified the logic to allow the parsing of shorter fixed width lines when using a line delimiter. We'll still attempt to parse the column values unless there is no content in which case a null will be produced. > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2896 > URL: https://issues.jboss.org/browse/TEIID-2896 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: TEIID-2896.patch > > > Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2014