[JBoss JIRA] (TEIID-4121) Enhancing the External Materialization
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4121?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4121:
---------------------------------------
You don't want to use a direct call for the MATVIEW_LOAD_SCRIPT - it should just be 'insert into ...'
Beyond that I don't see why the recursion check would fail here as the dynamic sql updateStmt doesn't invoke SYSADMIN.loadMatView. I'll try to reproduce this locally.
> Enhancing the External Materialization
> --------------------------------------
>
> Key: TEIID-4121
> URL: https://issues.jboss.org/browse/TEIID-4121
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.0
>
>
> The intention of move "status" table to physical database is to increase durable and fully control refresh and loading, but it increase the complexity.
> The "status" table by design should unique for whole VDB, if you look the https://teiid.gitbooks.io/documents/content/caching/External_Materializat..., the table structure:
> {code:sql}
> CREATE TABLE status
> (
> VDBName varchar(50) not null,
> VDBVersion integer not null,
> SchemaName varchar(50) not null,
> Name varchar(256) not null,
> TargetSchemaName varchar(50),
> TargetName varchar(256) not null,
> Valid boolean not null,
> LoadState varchar(25) not null,
> Cardinality long,
> Updated timestamp not null,
> LoadNumber long not null,
> PRIMARY KEY (VDBName, VDBVersion, SchemaName, Name)
> );
> {code}
> but currently, one VDB may have multiple "status" table, each view may have it's own "status" table. Further more, we can consider create status table automatically, which like internal, status create once VDB start, and configured in VDB scope.
> From finishedDeployment logic in MaterializationManager, MATERIALIZED_TABLE be used to determine whether the Mat is internal or external, But we lack the validation in metadata loading, in my previous test, the Internal Mat view configured lots of external view's properties like "status" table, the validation not throw excepton.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (TEIID-4232) Wrong detection of recursive plans when same aliases are used in nested CTEs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4232?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4232:
----------------------------------
Affects Version/s: 9.0
> Wrong detection of recursive plans when same aliases are used in nested CTEs
> ----------------------------------------------------------------------------
>
> Key: TEIID-4232
> URL: https://issues.jboss.org/browse/TEIID-4232
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0
> Reporter: Salvatore R
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> I defined the following view:
> {code:sql}
> create view v1 as
> WITH mycte as (SELECT 1 as col1) SELECT col1 FROM mycte;
> {code}
> If I run this query:
> {code:sql}
> WITH mycte as (SELECT * FROM views.v1) SELECT * from mycte ;
> {code}
> it fails on generate the query plan with this exception:
> {code}
> TEIID31124 Recursive plan detected. Command type Query was already issued against mycte. Planning cycle: [Query mycte, Query views.v1]
> {code}
> Using /*+ no_inline */ hint to prevent the inlining doesn't fail and returns the correct result.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (TEIID-4232) Wrong detection of recursive plans when same aliases are used in nested CTEs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4232?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4232.
-----------------------------------
Fix Version/s: 9.0
Resolution: Done
Removed the planning stack entry for inlined with.
> Wrong detection of recursive plans when same aliases are used in nested CTEs
> ----------------------------------------------------------------------------
>
> Key: TEIID-4232
> URL: https://issues.jboss.org/browse/TEIID-4232
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0
> Reporter: Salvatore R
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> I defined the following view:
> {code:sql}
> create view v1 as
> WITH mycte as (SELECT 1 as col1) SELECT col1 FROM mycte;
> {code}
> If I run this query:
> {code:sql}
> WITH mycte as (SELECT * FROM views.v1) SELECT * from mycte ;
> {code}
> it fails on generate the query plan with this exception:
> {code}
> TEIID31124 Recursive plan detected. Command type Query was already issued against mycte. Planning cycle: [Query mycte, Query views.v1]
> {code}
> Using /*+ no_inline */ hint to prevent the inlining doesn't fail and returns the correct result.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (TEIID-3822) Enable Server SNI support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3822?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3822.
-----------------------------------
Fix Version/s: (was: 8.12.x)
Resolution: Incomplete Description
Marking as incomplete description as it's not clear that there is anything more to do for this.
> Enable Server SNI support
> -------------------------
>
> Key: TEIID-3822
> URL: https://issues.jboss.org/browse/TEIID-3822
> Project: Teiid
> Issue Type: Sub-task
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> Adding a separate task for server support. Our current mechanism does allow for choosing a key based upon a configured alias, but not upon the explicit (Java 1.8) SNI hostname based logic.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (TEIID-4234) Gradle blueprint
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4234?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4234:
---------------------------------------
We'll investigate this for 9.0/9.x. Are you referring to https://issues.jboss.org/browse/TEIID-4094 about the JDBC driver? It would good to have as much explanation as possible as to the issues that you saw as they can be addressed individually as well.
> Gradle blueprint
> ----------------
>
> Key: TEIID-4234
> URL: https://issues.jboss.org/browse/TEIID-4234
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Reporter: jay vyas
> Assignee: Steven Hawkins
> Fix For: 9.0
>
> Attachments: build.gradle
>
>
> As a app developer, I'd like to spin up a teiid/JDV application with all client-side dependencies
> without needing to use an IDE.
> Currently, most of the TEiid resources and videos are based on IDE features, bootstrapping teiid on the local machine.
> Ideally, we might host a simple Teiid server that can run in a dockerfile with sample data, along side a gradle runnable file.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (TEIID-4234) Gradle blueprint
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4234?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4234:
----------------------------------
Fix Version/s: 9.0
(was: 8.13.5)
> Gradle blueprint
> ----------------
>
> Key: TEIID-4234
> URL: https://issues.jboss.org/browse/TEIID-4234
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Reporter: jay vyas
> Assignee: Steven Hawkins
> Fix For: 9.0
>
> Attachments: build.gradle
>
>
> As a app developer, I'd like to spin up a teiid/JDV application with all client-side dependencies
> without needing to use an IDE.
> Currently, most of the TEiid resources and videos are based on IDE features, bootstrapping teiid on the local machine.
> Ideally, we might host a simple Teiid server that can run in a dockerfile with sample data, along side a gradle runnable file.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (TEIID-4220) Unsupported encoding when POSTing to odata on Windows
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4220?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4220:
-------------------------------------
yeah, there is no reference to the supporting encoding in the ATOM portion of the spec.
> Unsupported encoding when POSTing to odata on Windows
> -----------------------------------------------------
>
> Key: TEIID-4220
> URL: https://issues.jboss.org/browse/TEIID-4220
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.x
> Reporter: Andrej Šmigala
> Assignee: Steven Hawkins
> Priority: Critical
>
> When posting to a windows server from a windows client, the default encoding is cp1252. When an xml request such as this is posted:
> {code:xml}
> <?xml version='1.0' encoding='cp1252'?><entry xmlns="http://www.w3.org/2005/Atom" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata" xmlns:d="http://docs.oasis-open.org/odata/ns/data" xmlns:gml="http://www.opengis.net/gml" xmlns:georss="http://www.georss.org/georss"><category scheme="http://docs.oasis-open.org/odata/ns/scheme"/>
> <content type="application/xml">
> <m:properties>
> <d:intkey m:type="Int32">4</d:intkey>
> <d:intnum m:type="Int32">4</d:intnum>
> <d:stringkey>4</d:stringkey>
> <d:stringval>value_4</d:stringval>
> <d:booleanval m:type="Boolean">false</d:booleanval>
> <d:decimalval m:type="Double">-20.4</d:decimalval>
> <d:timeval m:type="TimeOfDay">00:00:04</d:timeval>
> <d:dateval m:type="Date">2004-04-04</d:dateval>
> <d:timestampval m:type="DateTimeOffset">2004-01-01T00:00:04Z</d:timestampval>
> </m:properties>
> </content>
> </entry>
> {code}
> the following error is logged in the server:
> {noformat}
> 09:54:38,069 WARN [org.teiid.ODATA] (http-/0.0.0.0:8080-1) TEIID16050 Unable to process odata request due to: An I/O exception occurred. with cause Unsupported encoding: IBM1252: Unsupported encoding: IBM1252
> at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.entity(ODataXmlDeserializer.java:592)
> at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.getEntityFromClient(DataRequest.java:367)
> at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:359)
> at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:255)
> at org.apache.olingo.server.core.ServiceDispatcher.internalExecute(ServiceDispatcher.java:160)
> at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:98)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:66)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:43) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:226) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_79]
> Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: IBM1252
> at com.ctc.wstx.io.StreamBootstrapper.bootstrapInput(StreamBootstrapper.java:247)
> at com.ctc.wstx.stax.WstxInputFactory.doCreateSR(WstxInputFactory.java:546)
> at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:600)
> at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:615)
> at com.ctc.wstx.stax.WstxInputFactory.createXMLEventReader(WstxInputFactory.java:269)
> at __redirected.__XMLInputFactory.createXMLEventReader(__XMLInputFactory.java:170) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.getReader(ODataXmlDeserializer.java:97)
> at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.entity(ODataXmlDeserializer.java:583)
> ... 26 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (TEIID-4234) Gradle blueprint
by jay vyas (JIRA)
[ https://issues.jboss.org/browse/TEIID-4234?page=com.atlassian.jira.plugin... ]
jay vyas edited comment on TEIID-4234 at 5/31/16 1:16 PM:
----------------------------------------------------------
Example of what i built to solve this problem. In particular it was tricky to find the right maven deps combination (Teeid jdbc driver is hidden and there are transitive red hat deps that can trip things up).
If we publish this alongside a simple teiid server dockerfile, it would be a really natural experience for attracting java app developers to the data virt community.
the source code isnt attached for the java parts, because after all that is pretty easy to write (class.ForName the teiid driver and issue a sql query).
was (Author: jayunit100):
Example of what i built to solve this problem. In particular it was tricky to find the right maven deps combination (Teeid jdbc driver is hidden and there are transitive red hat deps that can trip things up).
If we publish this alongside a simple teiid server dockerfile, it would be a really natural experience for attracting java app developers to the data virt community.
the source code isnt attached for the java parts, because after all that is pretty easy to write (class.ForName the teiid driver and issue a sql query).
{quote}
{{
group 'd.analytics'
version '1.0-SNAPSHOT'
apply plugin: 'java'
apply plugin: 'idea'
apply plugin:'application'
/***
*
* Boilerplate for a 1.8 java app
*/
sourceCompatibility = 1.8
// mainClassName = "poc.TeiidInternalJDBC"
mainClassName = "poc.TeiidSpark"
startScripts {
applicationDefaultJvmArgs = ["-Xms4g","-Xmx4g"]
}
sourceCompatibility = 1.8
version = '1.0'
manifest {
attributes 'Main-Class': mainClassName
}
task fatJar(type: Jar) {
manifest {
attributes 'Implementation-Title': 'Gradle Jar File Example',
'Implementation-Version': version,
'Main-Class': mainClassName
}
baseName = project.name + '-all'
from { configurations.compile.collect { it.isDirectory() ? it : zipTree(it) } }
with jar
}
repositories {
mavenCentral()
maven{
url "https://repository.jboss.org/"
}
maven {
url "https://repository.jboss.org/nexus/content/repositories/releases/"
}
maven {
url "http://repository.jboss.org/nexus/content/groups/public/"
}
maven {
url "https://repository.jboss.org/nexus/content/repositories/thirdparty-uploads/"
}
maven {
url "http://repository.jboss.org/nexus/content/groups/developer/"
}
// necessary to avoid "Could not find org.jboss.as:jboss-as-parent:7.5.0.Final-redhat-15."
// not sure which ones we need, need to prune.
maven {
url "https://maven.repository.redhat.com/techpreview/all/"
}
maven {
url "https://maven.repository.redhat.com/earlyaccess/all/"
}
}
ext {
sparkVersion = "1.3.0"
scalaVersion = "2.10"
}
dependencies {
testCompile group: 'junit', name: 'junit', version: '4.11'
compile "org.jboss.teiid:teiid:8.9.1"
compile "org.jboss.teiid:teiid-client:8.9.1"
// compile "org.jboss.teiid:teiid:8.12.5"
// compile "org.jboss.teiid:teiid-client:8.12.5"
// compile "org.jboss.teiid:teiid:8.11.1"
// compile "org.jboss.teiid:teiid-client-jdbc:6.0.0"
// compile "org.jboss.teiid:teiid-client:8.11.1"
// compile "org.jboss.teiid:teiid-common-core:8.11.1"
compile "org.apache.spark:spark-core_${scalaVersion}:${sparkVersion}"
compile "org.apache.spark:spark-mllib_${scalaVersion}:${sparkVersion}"
compile "org.apache.spark:spark-network-shuffle_${scalaVersion}:${sparkVersion}"
compile "org.apache.spark:spark-sql_${scalaVersion}:${sparkVersion}"
compile "org.apache.spark:spark-graphx_${scalaVersion}:${sparkVersion}"
compile "org.apache.spark:spark-hive_${scalaVersion}:${sparkVersion}"
compile "joda-time:joda-time:2.7"
compile "org.json4s:json4s-jackson_2.10:3.1.0"
}
}}
{quote}
> Gradle blueprint
> ----------------
>
> Key: TEIID-4234
> URL: https://issues.jboss.org/browse/TEIID-4234
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Reporter: jay vyas
> Assignee: Steven Hawkins
> Fix For: 8.13.5
>
> Attachments: build.gradle
>
>
> As a app developer, I'd like to spin up a teiid/JDV application with all client-side dependencies
> without needing to use an IDE.
> Currently, most of the TEiid resources and videos are based on IDE features, bootstrapping teiid on the local machine.
> Ideally, we might host a simple Teiid server that can run in a dockerfile with sample data, along side a gradle runnable file.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months