[JBoss JIRA] (TEIID-5026) Add function to transform timestamp into Unix time
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5026?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-5026:
------------------------------------
[~shawkins] for the JDG integration there is a workaround with using string data type in source DDL instead of timestamps.
So this enhancement can be considered outside of that context.
> Add function to transform timestamp into Unix time
> --------------------------------------------------
>
> Key: TEIID-5026
> URL: https://issues.jboss.org/browse/TEIID-5026
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> Teiid supports function FROM_UNIXTIME as a result of TEIID-248.
> There isn't its reverse counterpart though.
> This is an issue, when there is a data source which doesn't support timestamp/date/time data types:
> * users choose to use long(unix time) in the source
> * by using FROM_UNIXTIME function they transform the long value (unix time) into respective data type value in their virtual model
> * they can read such source.
> * they can't insert/update it as this would require 'INSTEAD OF TRIGGER' with ability to transform timestamp/time/date back to long value - Unix time. This part is missing.
> As an example could serve [MySQL's UNIX_TIMESTAMP|https://dev.mysql.com/doc/refman/5.5/en/date-and-time-func...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIID-5026) Add function to transform timestamp into Unix time
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5026?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5026:
---------------------------------------
> So this enhancement can be considered exactly that.
My confusion is that this seemed to stem from JDG integration, which seems like it would use millis/longs instead.
Looking at this more, I think our implementation of from_unixtime is not correct. The other vendors use it as a conversion to string, not to timestamp - although in many contexts that distinction won't matter. I'll see if there is a way to rationalize all of this.
> Add function to transform timestamp into Unix time
> --------------------------------------------------
>
> Key: TEIID-5026
> URL: https://issues.jboss.org/browse/TEIID-5026
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> Teiid supports function FROM_UNIXTIME as a result of TEIID-248.
> There isn't its reverse counterpart though.
> This is an issue, when there is a data source which doesn't support timestamp/date/time data types:
> * users choose to use long(unix time) in the source
> * by using FROM_UNIXTIME function they transform the long value (unix time) into respective data type value in their virtual model
> * they can read such source.
> * they can't insert/update it as this would require 'INSTEAD OF TRIGGER' with ability to transform timestamp/time/date back to long value - Unix time. This part is missing.
> As an example could serve [MySQL's UNIX_TIMESTAMP|https://dev.mysql.com/doc/refman/5.5/en/date-and-time-func...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIID-5002) Use WildFly 11 Server Environment
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5002?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5002:
---------------------------------------
Netty deprecated a method when it actually should have been removed. In ObjectEncoder.AnonymousChunkedStream use:
{code}
public ByteBuf readChunk(ByteBufAllocator allocator) throws Exception {
ByteBuf cb = super.readChunk(allocator);
{code}
Instead of the old readChunk signature.
> Use WildFly 11 Server Environment
> ---------------------------------
>
> Key: TEIID-5002
> URL: https://issues.jboss.org/browse/TEIID-5002
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> Move the server environment to latest WildFly version 11
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIID-5026) Add function to transform timestamp into Unix time
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5026?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-5026:
------------------------------------
Like I indicated above. I've thought of this enhancement as adding the reverse option to FROM_UNIXTIME, which works with seconds. So this enhancement can be considered exactly that.
The MySQL implementation returns seconds.
PostgreSQL on the other hand offers more complex solution with using export function https://www.postgresql.org/docs/9.2/static/functions-datetime.html which is probably larger scope though.
> Add function to transform timestamp into Unix time
> --------------------------------------------------
>
> Key: TEIID-5026
> URL: https://issues.jboss.org/browse/TEIID-5026
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> Teiid supports function FROM_UNIXTIME as a result of TEIID-248.
> There isn't its reverse counterpart though.
> This is an issue, when there is a data source which doesn't support timestamp/date/time data types:
> * users choose to use long(unix time) in the source
> * by using FROM_UNIXTIME function they transform the long value (unix time) into respective data type value in their virtual model
> * they can read such source.
> * they can't insert/update it as this would require 'INSTEAD OF TRIGGER' with ability to transform timestamp/time/date back to long value - Unix time. This part is missing.
> As an example could serve [MySQL's UNIX_TIMESTAMP|https://dev.mysql.com/doc/refman/5.5/en/date-and-time-func...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIID-4992) Add OSDQ set functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4992?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-4992 at 9/6/17 8:11 PM:
---------------------------------------------------------------
[~osdq]The intersect and union operations are not symmetric. If you have:
{code}
String[] first = new String[]{"vivek16","abcd","vivek44", "x", "xx"};
String[] second = new String[]{"vivek36","vivekkk","abcd","vivek445", "x"};
//these will return different values
intersectionFuzzy(first,second,1);
intersectionFuzzy(second,first,1);
{code}
It seems like the logic should account for the fuzzing within both sets, such that these operations should be symmetrical.
was (Author: shawkins):
[~osdq]The intersect and union operations are not symmetric. If you have:
String[] first = new String[]{"vivek16","abcd","vivek44", "x", "xx"};
String[] second = new String[]{"vivek36","vivekkk","abcd","vivek445", "x"};
//these will return different values
intersectionFuzzy(first,second,1);
intersectionFuzzy(second,first,1);
It seems like the logic should account for the fuzzing within both sets, such that these operations should be symmetrical.
> Add OSDQ set functions
> ----------------------
>
> Key: TEIID-4992
> URL: https://issues.jboss.org/browse/TEIID-4992
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
> Attachments: SetUtil.java
>
>
> There will be a new osdq core library drop in maven central soon containing additional functions for Teiid to add.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIID-4992) Add OSDQ set functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4992?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4992:
---------------------------------------
[~osdq]The intersect and union operations are not symmetric. If you have:
String[] first = new String[]{"vivek16","abcd","vivek44", "x", "xx"};
String[] second = new String[]{"vivek36","vivekkk","abcd","vivek445", "x"};
//these will return different values
intersectionFuzzy(first,second,1);
intersectionFuzzy(second,first,1);
It seems like the logic should account for the fuzzing within both sets, such that these operations should be symmetrical.
> Add OSDQ set functions
> ----------------------
>
> Key: TEIID-4992
> URL: https://issues.jboss.org/browse/TEIID-4992
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
> Attachments: SetUtil.java
>
>
> There will be a new osdq core library drop in maven central soon containing additional functions for Teiid to add.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months