August 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5027) Translator infinispan-hotrod incorrect data type import

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5027?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5027: ------------------------------------ Shouldn't that be: CREATE FOREIGN TABLE instead of VIEW > Translator infinispan-hotrod incorrect data type import > ------------------------------------------------------- > > Key: TEIID-5027 > URL: https://issues.jboss.org/browse/TEIID-5027 > Project: Teiid > Issue Type: Bug > Components: JDG Connector, Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Blocker > > I have a vdb: > {code:xml|title=jdg71_crud-vdb.xml} > <vdb name="jdg71_crud" version="1"> > <model name="Source" type="PHYSICAL" visible="true"> > <source name="jdg7-source" translator-name="infinispan-hotrod" connection-jndi-name="java:/jdg71HotrodDS" /> > <metadata type="DDL"><![CDATA[ > CREATE VIEW SmallA ( > IntKey integer, > IntNum integer, > DoubleNum double, > ObjectValue object, > BigDecimalValue bigdecimal, > BigIntegerValue biginteger, > CharValue char, > StringNum string, > StringKey string PRIMARY KEY, > FloatNum float, > LongNum long, > TimeValue time, > ShortValue short, > ByteNum byte, > TimeStampValue timestamp, > BooleanValue boolean, > DateValue date) OPTIONS(UPDATABLE true, "teiid_ispn:cache" '${jdg.cache.name}'); > ]]> > </metadata> > <metadata type = "NATIVE"/> > </model> > </vdb> > {code} > But the resulting metadata are: > || column_name | column_type || > || IntKey | integer || > || IntNum | integer || > || DoubleNum | double || > || ObjectValue | string || > || BigDecimalValue | varbinary || > || BigIntegerValue | varbinary || > || CharValue | string || > || StringNum | string || > || StringKey | string || > || FloatNum | float || > || LongNum | long || > || TimeValue | varbinary || > || ShortValue | integer || > || ByteNum | integer || > || TimeStampValue | varbinary || > || BooleanValue | boolean || > || DateValue | varbinary || > All the columns should be replaced by appropriate data type as defined in the vdb. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5027) Translator infinispan-hotrod incorrect data type import

by Jan Stastny (JIRA)

Jan Stastny created TEIID-5027: ---------------------------------- Summary: Translator infinispan-hotrod incorrect data type import Key: TEIID-5027 URL: https://issues.jboss.org/browse/TEIID-5027 Project: Teiid Issue Type: Bug Components: JDG Connector, Misc. Connectors Affects Versions: 8.12.x-6.4 Reporter: Jan Stastny Assignee: Steven Hawkins Priority: Blocker I have a vdb: {code:xml|title=jdg71_crud-vdb.xml} <vdb name="jdg71_crud" version="1"> <model name="Source" type="PHYSICAL" visible="true"> <source name="jdg7-source" translator-name="infinispan-hotrod" connection-jndi-name="java:/jdg71HotrodDS" /> <metadata type="DDL"><![CDATA[ CREATE VIEW SmallA ( IntKey integer, IntNum integer, DoubleNum double, ObjectValue object, BigDecimalValue bigdecimal, BigIntegerValue biginteger, CharValue char, StringNum string, StringKey string PRIMARY KEY, FloatNum float, LongNum long, TimeValue time, ShortValue short, ByteNum byte, TimeStampValue timestamp, BooleanValue boolean, DateValue date) OPTIONS(UPDATABLE true, "teiid_ispn:cache" '${jdg.cache.name}'); ]]> </metadata> <metadata type = "NATIVE"/> </model> </vdb> {code} But the resulting metadata are: || column_name | column_type || || IntKey | integer || || IntNum | integer || || DoubleNum | double || || ObjectValue | string || || BigDecimalValue | varbinary || || BigIntegerValue | varbinary || || CharValue | string || || StringNum | string || || StringKey | string || || FloatNum | float || || LongNum | long || || TimeValue | varbinary || || ShortValue | integer || || ByteNum | integer || || TimeStampValue | varbinary || || BooleanValue | boolean || || DateValue | varbinary || All the columns should be replaced by appropriate data type as defined in the vdb. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5026) Add function to transform timestamp into Unix time

by Jan Stastny (JIRA)

Jan Stastny created TEIID-5026: ---------------------------------- Summary: 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 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)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5024) Embedded soapservice fails with cxf jaxb class not found

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5024?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5024. ----------------------------------- Resolution: Done Updated the poms. > Embedded soapservice fails with cxf jaxb class not found > -------------------------------------------------------- > > Key: TEIID-5024 > URL: https://issues.jboss.org/browse/TEIID-5024 > Project: Teiid > Issue Type: Bug > Components: SOAP Services > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > The cxf-rt-databinding-jaxb dependency is needed for embedded soap connections. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5025) Improve BufferManagerCleaner shutdown

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5025: ------------------------------------- Summary: Improve BufferManagerCleaner shutdown Key: TEIID-5025 URL: https://issues.jboss.org/browse/TEIID-5025 Project: Teiid Issue Type: Quality Risk Components: Embedded Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0 When running an embedded example the static timer used for the buffer cleaner is a daemon thread that isn't otherwise shutdown and will cause a delay/warning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5024) Embedded soapservice fails with cxf jaxb class not found

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5024: ------------------------------------- Summary: Embedded soapservice fails with cxf jaxb class not found Key: TEIID-5024 URL: https://issues.jboss.org/browse/TEIID-5024 Project: Teiid Issue Type: Bug Components: SOAP Services Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0 The cxf-rt-databinding-jaxb dependency is needed for embedded soap connections. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5007) Changes to reduce Teiid in the cloud footprint

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5007: --------------------------------------- Made a commit to move saxon dependencies our of core classes, such as the Evaluator and Validator. That dependency as well as xom and nux can be left out of the runtime without error as long as xml functionality is not used. This can be abstracted further if need in a separate module. > Changes to reduce Teiid in the cloud footprint > ---------------------------------------------- > > Key: TEIID-5007 > URL: https://issues.jboss.org/browse/TEIID-5007 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.x > > > A Teiid instance even as swarm or springboot needs additional considerations to minimize the runtime footprint. This includes: > * container aware auto-sizing. Detection of the number of cpus and available memory need refined - there are experimental settings being considered for containerized vms to better report these values and there is logic in WildFly and other projects that attempts better auto-detection. We also need to utilize the memory buffer space more and probably as off-heap space (and ideally direct operations on the serialized data) > * Subsystems required include JTA, webserver, security, which could be satisfied by slimmer alternative versions - especially if we make new assumptions, such as not utilizing xa transactions. > * Engine dependencies could be application specific - removing xml/xsl support, geometry support, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5023) Amazon S3 translator contains java 1.8 feature for Base64

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5023?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-5023. -------------------------------- Fix Version/s: 8.12.x-6.4 Resolution: Done > Amazon S3 translator contains java 1.8 feature for Base64 > --------------------------------------------------------- > > Key: TEIID-5023 > URL: https://issues.jboss.org/browse/TEIID-5023 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 8.12.x-6.4 > > > The amazon s3 translator is using the java.util.Base64 java 1.8 feature. Changing it to use the teiid util Base64. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5023) Amazon S3 translator contains java 1.8 feature for Base64

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5023?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5023: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/1000 > Amazon S3 translator contains java 1.8 feature for Base64 > --------------------------------------------------------- > > Key: TEIID-5023 > URL: https://issues.jboss.org/browse/TEIID-5023 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > The amazon s3 translator is using the java.util.Base64 java 1.8 feature. Changing it to use the teiid util Base64. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5023) Amazon S3 translator contains java 1.8 feature for Base64

by Van Halbert (JIRA)

Van Halbert created TEIID-5023: ---------------------------------- Summary: Amazon S3 translator contains java 1.8 feature for Base64 Key: TEIID-5023 URL: https://issues.jboss.org/browse/TEIID-5023 Project: Teiid Issue Type: Task Components: Misc. Connectors Affects Versions: 8.12.x-6.4 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor The amazon s3 translator is using the java.util.Base64 java 1.8 feature. Changing it to use the teiid util Base64. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2017