[JBoss JIRA] (TEIID-4866) Enhance SQL Alchemy integration to work with Superset
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4866?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4866:
---------------------------------------
Made another round of updates. We will now default the server_version function to report PostgreSQL 8.2, rather than Teiid version - since that is required for sqlalchemy/superset and does not directly affect ODBC clients that use the server_version property. We should look into whether it makes sense to also set the server_version property to 8.2. Geometry and xml handling were also refined so that actual type name is used - however some clients won't utilize an xml type for a server version less than 8.3. The foreign key logic also needed further refinements.
> Enhance SQL Alchemy integration to work with Superset
> -----------------------------------------------------
>
> Key: TEIID-4866
> URL: https://issues.jboss.org/browse/TEIID-4866
> Project: Teiid
> Issue Type: Sub-task
> Components: ODBC
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3
>
>
> Superset (previously Caravel) integration allows for an expanded set of sources, which was requested https://github.com/airbnb/superset/issues/241
> After some initial testing it looks like we still have some type and other issues to address.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4896) Two VDB's referencing same teiid_ispn:cache is not using the same cache
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4896?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4896:
-------------------------------
Attachment: jdg-remote-cache-ddl-vdb.xml
jdg-remote-cache-registered-pb-vdb.xml
> Two VDB's referencing same teiid_ispn:cache is not using the same cache
> -----------------------------------------------------------------------
>
> Key: TEIID-4896
> URL: https://issues.jboss.org/browse/TEIID-4896
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 9.3.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: jdg-remote-cache-ddl-vdb.xml, jdg-remote-cache-registered-pb-vdb.xml
>
>
> I have 2 VDB's where they both reference the same cache using OPTIONS property:
> "teiid_ispn:cache" 'datasourceCache'
> However, when I insert into one VDB, its not seen by the other VDB.
> This was testing out the translators ability to use an already registered protobuf in Infinispan.
> The first VDB (jdg-remote-cache-vdb.xml) was deployed and then inserted and selected the results. This registered the protobuf.
> The second VDB (jdg-remote-cache-registered-pb-vdb.xml) was then deployed and was expecting to be able to read the same cache. The metadata was derived correctly, but it appears that one of the two are using the default cache, not the specified cache.
> I'll attach the vdb's.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4896) Two VDB's referencing same teiid_ispn:cache is not using the same cache
by Van Halbert (JIRA)
Van Halbert created TEIID-4896:
----------------------------------
Summary: Two VDB's referencing same teiid_ispn:cache is not using the same cache
Key: TEIID-4896
URL: https://issues.jboss.org/browse/TEIID-4896
Project: Teiid
Issue Type: Bug
Components: JDG Connector
Affects Versions: 9.3.1
Reporter: Van Halbert
Assignee: Steven Hawkins
I have 2 VDB's where they both reference the same cache using OPTIONS property:
"teiid_ispn:cache" 'datasourceCache'
However, when I insert into one VDB, its not seen by the other VDB.
This was testing out the translators ability to use an already registered protobuf in Infinispan.
The first VDB (jdg-remote-cache-vdb.xml) was deployed and then inserted and selected the results. This registered the protobuf.
The second VDB (jdg-remote-cache-registered-pb-vdb.xml) was then deployed and was expecting to be able to read the same cache. The metadata was derived correctly, but it appears that one of the two are using the default cache, not the specified cache.
I'll attach the vdb's.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4863) Run teiid embedded via Wildfly Swarm and Spring Boot
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4863?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4863:
-------------------------------------
1) What is WildFly Swarm relation here, this JIRA should be targeting Spring Boot? The main thing to focus here is the differences between WF Swarm and Spring Boot based Teiid embedded should be as minimalistic as possible.
2) Like in Spring Boot, is there way to we can envision bootstrapping of embedded code, where data sources are defined based on the dependencies added? I am not sure how Spring figures out the configuration like URL, credentials etc. I am looking to hide away current scaffolding code, and make embedded based on single defined VDB file like database.ddl, all user ever interacts is this DDL file. Everything should be gleaned from this file as default, and some configuration details could be overridden based on environment variables. Then this would fit in with MicroServices.
> Run teiid embedded via Wildfly Swarm and Spring Boot
> ----------------------------------------------------
>
> Key: TEIID-4863
> URL: https://issues.jboss.org/browse/TEIID-4863
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Affects Versions: 10.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 10.0
>
>
> WildFly Swarm can use simple pojo to integrate framework, which compatible with EmbeddedConfiguration, actually this is encouraged way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4895) Determine community requirements for WildFly usage
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4895:
-------------------------------------
Summary: Determine community requirements for WildFly usage
Key: TEIID-4895
URL: https://issues.jboss.org/browse/TEIID-4895
Project: Teiid
Issue Type: Task
Reporter: Steven Hawkins
Assignee: Steven Hawkins
WildFly is typically the runtime for Teiid. However we want feedback from the community on what style of WildFly integration is important:
- The ability to deploy Teiid into a managed WildFly instance/cluster
- The combination Teiid/WildFly artifact
- A layered docker image
- Not full WildFly, just Swarm
- Not needed, just Embedded
Based upon this we can better tune our documentation, downloads, and examples.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4894) Remove xml document models
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4894:
-------------------------------------
Summary: Remove xml document models
Key: TEIID-4894
URL: https://issues.jboss.org/browse/TEIID-4894
Project: Teiid
Issue Type: Task
Components: Documentation, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.0
XML document models have been deprecated for a full release and are not expected to have tooling support in any future UI. Support should be removed from the server side.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months