[JBoss JIRA] (TEIID-3547) Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3547?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3547.
---------------------------------
> Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3547
> URL: https://issues.jboss.org/browse/TEIID-3547
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> Oracle translator seems to support translation of patterns from SimpleDateFormat to oracle's patterns [1], but not for all of them [2]. If Teiid is not able to translate format then it retrieves date/time/timestamp field and format it [2]. However, if pattern ends with non-pattern/non-letter character, pattern is translated only partially and passed to Oracle DB [3] - I have tried number, *, /, \, etc. Similar behavior with postgresql translator
> [1]
> *Query:* select formattimestamp(timestampvalue, 'y') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'YYYY') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> [2]
> *Query:* select formattimestamp(timestampvalue, 'D') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> [3]
> *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s-') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'AD-YYYY-------Dy-AM-------') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[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.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3524) Database Logging not working
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3524?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3524.
---------------------------------
> Database Logging not working
> ----------------------------
>
> Key: TEIID-3524
> URL: https://issues.jboss.org/browse/TEIID-3524
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Fix For: 8.7.1.6_2, 8.11
>
>
> When using db logging in Teiid, nothing gets inserted into the db. Logs appear at server.log, but not in the db.
> I set up the logging as follows:
> Created java:/teiid-log-ds datasource.
> Added these to logging subsystem:
> {code:xml}
> <async-handler name="TEIID_COMMAND_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <async-handler name="TEIID_AUDIT_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <custom-handler name="TEIID_JPA_LOG" class="org.teiid.logger.DatabaseAppender" module="org.jboss.teiid.extensions">
> <level name="DEBUG"/>
> </custom-handler>
> <logger category="org.teiid.COMMAND_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_COMMAND_LOG"/>
> </handlers>
> </logger>
> <logger category="org.teiid.AUDIT_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_AUDIT_LOG"/>
> </handlers>
> </logger>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3407) Clarify in the README's for each quickstart regarding how to start the server
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3407?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3407.
---------------------------------
> Clarify in the README's for each quickstart regarding how to start the server
> -----------------------------------------------------------------------------
>
> Key: TEIID-3407
> URL: https://issues.jboss.org/browse/TEIID-3407
> Project: Teiid
> Issue Type: Enhancement
> Components: Quick Starts
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Trivial
>
> Change the start command in the README's to be the following:
> To start the server, open a command line and navigate to the "bin" directory under the root directory of the JBoss server and run:
>
> For Linux: ./standalone.sh
> for Windows: standalone.bat
> append the following to the command to indicate which configuration to use if Teiid isn't configured in the default configuration
>
> -c standalone-teiid.xml
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3584) NoSuchMethodError when issuing show plan request -IBM JDK 1.6
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3584?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3584.
---------------------------------
> NoSuchMethodError when issuing show plan request -IBM JDK 1.6
> -------------------------------------------------------------
>
> Key: TEIID-3584
> URL: https://issues.jboss.org/browse/TEIID-3584
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.7.1
> Environment: IBM JDK 1.6
> Reporter: Filip Elias
> Assignee: Steven Hawkins
>
> Teiid client throws an error[1] when processing "show plan;" request. This issue exist only on IBM jdk 1.6. The error is thrown at client side.
> [1]
> {code}
> Exception in thread "main" java.lang.NoSuchMethodError: javax/xml/stream/XMLOutputFactory.newFactory()Ljavax/xml/stream/XMLOutputFactory;
> at org.teiid.client.plan.PlanNode.toXml(PlanNode.java:175)
> at org.teiid.jdbc.StatementImpl.executeShow(StatementImpl.java:556)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:502)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:393)
> at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327)
> at JDBCClient.execute(JDBCClient.java:93)
> at JDBCClient.main(JDBCClient.java:47)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3419) Add ability to set a default role across all VDBs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3419?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3419.
---------------------------------
> Add ability to set a default role across all VDBs
> -------------------------------------------------
>
> Key: TEIID-3419
> URL: https://issues.jboss.org/browse/TEIID-3419
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> There should be an ability to either set a default role across the server, or to restrict access by default. For example, all VDBs have a default user role that is applied before the VDB specific roles are. Alternatively, there could be a system wide flag that toggles the behavior of VDBs when no roles are defined between accessible to all or denied to all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months