[JBoss JIRA] (TEIID-3197) Fix install script on RHEL 6.5
by Tom Arnold (JIRA)
Tom Arnold created TEIID-3197:
---------------------------------
Summary: Fix install script on RHEL 6.5
Key: TEIID-3197
URL: https://issues.jboss.org/browse/TEIID-3197
Project: Teiid
Issue Type: Bug
Components: Build/Kits
Reporter: Tom Arnold
Assignee: Steven Hawkins
install.sh script fails on RHEL 6.5 system because of older versions of xmllint and coreutils.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-3121) Teiid Standalone Server
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin... ]
Tom Arnold commented on TEIID-3121:
-----------------------------------
Okay, I will check it out. Thanks!
> Teiid Standalone Server
> -----------------------
>
> Key: TEIID-3121
> URL: https://issues.jboss.org/browse/TEIID-3121
> Project: Teiid
> Issue Type: Feature Request
> Components: Build/Kits
> Reporter: Tom Arnold
> Fix For: Open To Community
>
>
> Perform the server installation steps as part of the build and add the result to the downloads page. It seems like this is something that everyone who isn't using the embedded kit has to do anyways, and would hopefully eliminate confusion caused by people trying to deploy the runtime in unsupported versions of JBoss.
> * Teiid Runtime
> * Teiid Web Console
> * JBoss EAP 6.1 Alpha
> * Resteasy JAX-RS Patch
> End result would simplify the installation process to:
> 1. Unzip Teiid server.
> 2. Run `bin/add-user.sh` script.
> 3. Deploy custom translators, VDB, etc.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-3121) Teiid Standalone Server
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3121:
-------------------------------------
With EAP 6.3.0.Alpha move, I wanted to see if I can replace your install.sh with a maven script as we talked about. But idiosyncrasies with maven assembly and maven build did not let me finish the task. I commented the code in the build/pom.xml if you are interested in taking crack at it. I know I can easily do with using ant plugin, but wanted avoid ant plug-in. The last zipping of the artifact is in question.
> Teiid Standalone Server
> -----------------------
>
> Key: TEIID-3121
> URL: https://issues.jboss.org/browse/TEIID-3121
> Project: Teiid
> Issue Type: Feature Request
> Components: Build/Kits
> Reporter: Tom Arnold
> Fix For: Open To Community
>
>
> Perform the server installation steps as part of the build and add the result to the downloads page. It seems like this is something that everyone who isn't using the embedded kit has to do anyways, and would hopefully eliminate confusion caused by people trying to deploy the runtime in unsupported versions of JBoss.
> * Teiid Runtime
> * Teiid Web Console
> * JBoss EAP 6.1 Alpha
> * Resteasy JAX-RS Patch
> End result would simplify the installation process to:
> 1. Unzip Teiid server.
> 2. Run `bin/add-user.sh` script.
> 3. Deploy custom translators, VDB, etc.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-3121) Teiid Standalone Server
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin... ]
Tom Arnold commented on TEIID-3121:
-----------------------------------
It looks like some work has been done on Maven approach as part of TEIID-3185. Can anyone comment?
> Teiid Standalone Server
> -----------------------
>
> Key: TEIID-3121
> URL: https://issues.jboss.org/browse/TEIID-3121
> Project: Teiid
> Issue Type: Feature Request
> Components: Build/Kits
> Reporter: Tom Arnold
> Fix For: Open To Community
>
>
> Perform the server installation steps as part of the build and add the result to the downloads page. It seems like this is something that everyone who isn't using the embedded kit has to do anyways, and would hopefully eliminate confusion caused by people trying to deploy the runtime in unsupported versions of JBoss.
> * Teiid Runtime
> * Teiid Web Console
> * JBoss EAP 6.1 Alpha
> * Resteasy JAX-RS Patch
> End result would simplify the installation process to:
> 1. Unzip Teiid server.
> 2. Run `bin/add-user.sh` script.
> 3. Deploy custom translators, VDB, etc.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-3193) Teiid not removing/setting the correct TCCL before calling getMetadata on translator
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3193?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3193.
---------------------------------
Labels: CR3 (was: )
Resolution: Done
Fixed the failing unit tests, merged to 8.9.
> Teiid not removing/setting the correct TCCL before calling getMetadata on translator
> ------------------------------------------------------------------------------------
>
> Key: TEIID-3193
> URL: https://issues.jboss.org/browse/TEIID-3193
> Project: Teiid
> Issue Type: Bug
> Components: Common
> Affects Versions: 8.8
> Reporter: Michael Farwell
> Assignee: Ramesh Reddy
> Labels: CR3
> Fix For: 8.9
>
>
> Ramesh helped me debug a class loading issue that I'm experiencing with a custom translator and asked me to open this ticket based on his findings. The forum link is specified below and contains all of the necessary information.
> Ramesh's words: "OK, I believe the geoTools is using the TCCL to load the schema, thus the error. However, the error is on the Teiid side not correctly removing/setting the correct TCCL before we call "getMetadata" call on the translator. You can add JIRA for this we will fix it."
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-3196) Remove Teradata join pushdown restriction
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3196?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3196.
-----------------------------------
Resolution: Done
The default restriction has been removed. For older branches users can manually set the translator property supportsOuterJoins = true.
> Remove Teradata join pushdown restriction
> -----------------------------------------
>
> Key: TEIID-3196
> URL: https://issues.jboss.org/browse/TEIID-3196
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Connector
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> Teradata is marked as not supporting outer joins. It looks like this should be at most just full outer joins based upon the older code. But it's possible that the restriction is not needed at all based upon the Teradata docs.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-3193) Teiid not removing/setting the correct TCCL before calling getMetadata on translator
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3193?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3193:
-------------------------------------
Good call on PolicyDecider/AuthorizationValidator, I forgot about those.
See this pull https://github.com/teiid/teiid/pull/353 let me know if you want me make any more additions. If you think these are too late for 8.9, I am Ok with we targeting to 8.10
> Teiid not removing/setting the correct TCCL before calling getMetadata on translator
> ------------------------------------------------------------------------------------
>
> Key: TEIID-3193
> URL: https://issues.jboss.org/browse/TEIID-3193
> Project: Teiid
> Issue Type: Bug
> Components: Common
> Affects Versions: 8.8
> Reporter: Michael Farwell
> Assignee: Ramesh Reddy
> Fix For: 8.9
>
>
> Ramesh helped me debug a class loading issue that I'm experiencing with a custom translator and asked me to open this ticket based on his findings. The forum link is specified below and contains all of the necessary information.
> Ramesh's words: "OK, I believe the geoTools is using the TCCL to load the schema, thus the error. However, the error is on the Teiid side not correctly removing/setting the correct TCCL before we call "getMetadata" call on the translator. You can add JIRA for this we will fix it."
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months