[JBoss JIRA] (TEIID-3829) olingo module junit test failed
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3829?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3829:
-------------------------------------
sure, go ahead
> olingo module junit test failed
> -------------------------------
>
> Key: TEIID-3829
> URL: https://issues.jboss.org/browse/TEIID-3829
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.13
> Reporter: Kylin Soong
> Assignee: Ramesh Reddy
> Fix For: 8.13
>
>
> olingo module junit test failed:
> {code}
> Results :
> Failed tests:
> TestODataSQLBuilder.testEq:431->te:400->helpTest:227 expected:<...g0 WHERE g0.e1 = {t'[04]:20:02'} ORDER BY g0...> but was:<...g0 WHERE g0.e1 = {t'[16]:20:02'} ORDER BY g0...>
> TestODataSQLBuilder.testTimeMethods:552->te:400->helpTest:227 expected:<...YEAR({ts'2008-10-13 [04]:20:02.0'}) = 2008 O...> but was:<...YEAR({ts'2008-10-13 [16]:20:02.0'}) = 2008 O...>
> Tests run: 109, Failures: 2, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3829) olingo module junit test failed
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3829?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3829:
---------------------------------------
Should I go ahead and check in a fix here?
> olingo module junit test failed
> -------------------------------
>
> Key: TEIID-3829
> URL: https://issues.jboss.org/browse/TEIID-3829
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.13
> Reporter: Kylin Soong
> Assignee: Ramesh Reddy
> Fix For: 8.13
>
>
> olingo module junit test failed:
> {code}
> Results :
> Failed tests:
> TestODataSQLBuilder.testEq:431->te:400->helpTest:227 expected:<...g0 WHERE g0.e1 = {t'[04]:20:02'} ORDER BY g0...> but was:<...g0 WHERE g0.e1 = {t'[16]:20:02'} ORDER BY g0...>
> TestODataSQLBuilder.testTimeMethods:552->te:400->helpTest:227 expected:<...YEAR({ts'2008-10-13 [04]:20:02.0'}) = 2008 O...> but was:<...YEAR({ts'2008-10-13 [16]:20:02.0'}) = 2008 O...>
> Tests run: 109, Failures: 2, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3839) minimize implicit dependencies on sun classes
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3839?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3839.
-----------------------------------
Fix Version/s: 8.13
Resolution: Done
Updated the logon result class to prevent a classnotfound exception and to send the timezone id so that newer client won't need the sun.jdk module dependency.
> minimize implicit dependencies on sun classes
> ---------------------------------------------
>
> Key: TEIID-3839
> URL: https://issues.jboss.org/browse/TEIID-3839
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Driver, Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.3
>
>
> Serialization of the server timezone can rely on sun.util.calendar.Zoneinfo, which is not allowed by default in EAP/Wildfly if using the driver as just a jar. Ideally we should avoid direct serialization of these classes as much as possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3839) minimize implicit dependencies on sun classes
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3839:
-------------------------------------
Summary: minimize implicit dependencies on sun classes
Key: TEIID-3839
URL: https://issues.jboss.org/browse/TEIID-3839
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Driver, Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12.3
Serialization of the server timezone can rely on sun.util.calendar.Zoneinfo, which is not allowed by default in EAP/Wildfly if using the driver as just a jar. Ideally we should avoid direct serialization of these classes as much as possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3837) AS400 deployVDB
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3837?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3837:
-------------------------------------
[~mtawk] this should have been a forum question, not a jira :(
I believe the metadata download from your AS400 is taking long time considering the large number of tables. If you already have the schema, you can define the tables inside your dynamic vdb, so that you can avoid the load of the metadata. See one of our DDL based Dynamic VDB examples
> AS400 deployVDB
> ---------------
>
> Key: TEIID-3837
> URL: https://issues.jboss.org/browse/TEIID-3837
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
>
> I'm using Teiid 8.11.3 and db2i translator,
> I'm connecting to an AS400 DB containing around 1000 tables, the deployvdb remained running for 2 hours and it did not finish.
> Is there a way to speed up the deployvdb treatment? or to know more details on the vdb deployment progress?
> I'm able to fetch the DB information schema via a jdbc connection and it is not taking that much time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3829) olingo module junit test failed
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3829?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3829:
---------------------------------------
It's just an issue with the locale:
{code}
public static void main(String[] args) {
for (String id : TimeZone.getAvailableIDs()) {
TimeZone.setDefault(TimeZone.getTimeZone(id));
try {
new TestODataSQLBuilder().testEq();
} catch (Throwable e) {
System.out.println(id);
}
}
}
{code}
We just need to add a setup/teardown that sets the system timezone to something that is known, such as the tests that use TimestampWithTimezone.resetCalendar.
> olingo module junit test failed
> -------------------------------
>
> Key: TEIID-3829
> URL: https://issues.jboss.org/browse/TEIID-3829
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.13
> Reporter: Kylin Soong
> Assignee: Ramesh Reddy
> Fix For: 8.13
>
>
> olingo module junit test failed:
> {code}
> Results :
> Failed tests:
> TestODataSQLBuilder.testEq:431->te:400->helpTest:227 expected:<...g0 WHERE g0.e1 = {t'[04]:20:02'} ORDER BY g0...> but was:<...g0 WHERE g0.e1 = {t'[16]:20:02'} ORDER BY g0...>
> TestODataSQLBuilder.testTimeMethods:552->te:400->helpTest:227 expected:<...YEAR({ts'2008-10-13 [04]:20:02.0'}) = 2008 O...> but was:<...YEAR({ts'2008-10-13 [16]:20:02.0'}) = 2008 O...>
> Tests run: 109, Failures: 2, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month