October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3737) Allow date formatted string literals to be parsed as timestamps

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3737: ------------------------------------- Summary: Allow date formatted string literals to be parsed as timestamps Key: TEIID-3737 URL: https://issues.jboss.org/browse/TEIID-3737 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 For consistency with most major vendors we should support allowing date literals to be parsed as timestamps. For example: timestamp_col > '2001-01-01' which would prevent the predicate from being resolved as a string comparison. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3736) Allow date formatted string literals to be parsed as timestamps

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3736: ------------------------------------- Summary: Allow date formatted string literals to be parsed as timestamps Key: TEIID-3736 URL: https://issues.jboss.org/browse/TEIID-3736 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 For consistency with most major vendors we should support allowing date literals to be parsed as timestamps. For example: timestamp_col > '2001-01-01' which would prevent the predicate from being resolved as a string comparison. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3731) Introduce an alternative protocol to lessen the usage of java serialization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3731?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3731: --------------------------------------- There are several reasons. The first is that whatever is missing is quite a lot of stuff. Standard logic would need remapped (especially around cursoring, sessioning, and exception handling), streaming hasn't been implemented, type handling would need to be expanded, the teiid JDBC extensions would need reimplemented - and the asynch stuff does not fit well. And of course we still would be providing our own JDBC client so it's not like we would own significantly less code. The other reason is that we'll still need to provide a backwards compatible transport for the whole release, so we'd continue to have all the existing messaging classes as well. > Introduce an alternative protocol to lessen the usage of java serialization > --------------------------------------------------------------------------- > > Key: TEIID-3731 > URL: https://issues.jboss.org/browse/TEIID-3731 > Project: Teiid > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > Even with heavy usage of externalizable there is still an overhead to java serialization blocking and reference tracking. With custom object input/output we can eliminate the need for java serialization with most messages. > This however would need to work beside the existing java serialization protocol for backwards compatibility. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3727) Add a latest version of the salesforce connectivity to the server kit

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3727?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3727: ------------------------------------- I added it as separate repo module, instead of in Teiid repo. Would need to do few modifications before pull can be issued. Let me see if I can fix and and send the pull request > Add a latest version of the salesforce connectivity to the server kit > --------------------------------------------------------------------- > > Key: TEIID-3727 > URL: https://issues.jboss.org/browse/TEIID-3727 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > For convenience it would be good to offer a latest salesforce version, rather than requiring users to build a new translator/resource adapter. We can also deprecate the v22 connectivity then. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3731) Introduce an alternative protocol to lessen the usage of java serialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3731?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3731: ------------------------------------- Why not use Postgres all the way, implement whatever is missing? > Introduce an alternative protocol to lessen the usage of java serialization > --------------------------------------------------------------------------- > > Key: TEIID-3731 > URL: https://issues.jboss.org/browse/TEIID-3731 > Project: Teiid > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > Even with heavy usage of externalizable there is still an overhead to java serialization blocking and reference tracking. With custom object input/output we can eliminate the need for java serialization with most messages. > This however would need to work beside the existing java serialization protocol for backwards compatibility. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3727) Add a latest version of the salesforce connectivity to the server kit

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3727?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3727: --------------------------------------- Thanks, I'll go ahead and add it. Unless you want to do a pull request? > Add a latest version of the salesforce connectivity to the server kit > --------------------------------------------------------------------- > > Key: TEIID-3727 > URL: https://issues.jboss.org/browse/TEIID-3727 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > For convenience it would be good to offer a latest salesforce version, rather than requiring users to build a new translator/resource adapter. We can also deprecate the v22 connectivity then. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3727) Add a latest version of the salesforce connectivity to the server kit

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3727?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3727: ------------------------------------- Here is the version 34 I developed https://github.com/rareddy/salesforce > Add a latest version of the salesforce connectivity to the server kit > --------------------------------------------------------------------- > > Key: TEIID-3727 > URL: https://issues.jboss.org/browse/TEIID-3727 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > For convenience it would be good to offer a latest salesforce version, rather than requiring users to build a new translator/resource adapter. We can also deprecate the v22 connectivity then. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015