[JBoss JIRA] (TEIID-5131) Create ansible playbooks for the ansible service broker
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5131?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5131:
---------------------------------------
I'm not saying there is an issue. Only that I'm starting with the current state based upon the infinispan images / templates. Then I'll adjust things for swarm.
> Create ansible playbooks for the ansible service broker
> -------------------------------------------------------
>
> Key: TEIID-5131
> URL: https://issues.jboss.org/browse/TEIID-5131
> Project: Teiid
> Issue Type: Enhancement
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.1
>
>
> For some of the most common usage patterns, we should create playbooks that contribute service brokers via the ansible service broker. This could be:
> salesforce as db
> couchbase as db/odata
> mongodb as db/odata
> other openshift databases as odata
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5131) Create ansible playbooks for the ansible service broker
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5131?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5131:
---------------------------------------
I have emulated the infinispan approach to create an openshift image for our standalone-teiid.xml - infinispan adds a clustered.xml and cloud.xml to the wildfly standalone configurations and they also inject a configuration via the template.
The default security realm is used to add application and management users. This is fine for a first cut, but we'll need to have an option to support keycloak/openshift sso (especially for admin).
I should have this wired for just salesforce for jdbc access on Monday, such that the template will accept the sf credentials and handle the appropriate vdb / resource adapter configuration. I want to make sure I have a handle on exposing JDBC as a route and to validate clustering/ha with this template (although other than ha there won't be much benefit).
The next step will be to expose odata for an existing provisioned instance. I'm not sure if that can be done via templates or if ansible will be required.
> Create ansible playbooks for the ansible service broker
> -------------------------------------------------------
>
> Key: TEIID-5131
> URL: https://issues.jboss.org/browse/TEIID-5131
> Project: Teiid
> Issue Type: Enhancement
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.1
>
>
> For some of the most common usage patterns, we should create playbooks that contribute service brokers via the ansible service broker. This could be:
> salesforce as db
> couchbase as db/odata
> mongodb as db/odata
> other openshift databases as odata
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5133) XmlTable path language is not always identical to XPathValue expressions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5133?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-5133:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1508911
Bugzilla Update: Perform
> XmlTable path language is not always identical to XPathValue expressions
> ------------------------------------------------------------------------
>
> Key: TEIID-5133
> URL: https://issues.jboss.org/browse/TEIID-5133
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.2.7, 9.3.5
>
>
> The same Path value, used in XPathValue and XmlTable->Path brings different results.
> That is for the following query:
> {code:sql}
> Select * From
> (select '<root>
> <item>
> <id>id1</id>
> <val>val1</val>
> </item>
> </root>' as resp) w,
> XMLTABLE(
> '/root' passing XMLPARSE(document w.resp) columns
> valOption2 string PATH 'item[id = "id1"]/val'
> --,valOption1 string PATH 'item[id/text() = "id1"]/val'
> ) x;;
> {code}
> returned value for "valOption2" will be changed from "val1" to "null" that is incorrect and unexpected behavior.
> Using "node/text()" in Path expressions may result in side effects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5135) REPEAT function truncates strings to 4000 characters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5135?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5135:
----------------------------------
Issue Type: Quality Risk (was: Bug)
Priority: Minor (was: Critical)
The system has a max length for the string data type. That affects all functions evaluated in Teiid. You may adjust this with a system property if you have a different need org.teiid.maxStringLength - https://teiid.gitbooks.io/documents/content/admin/System_Properties.html
You should still keep it as constrained as possible as the string type for a live batch is always fully held in memory.
> REPEAT function truncates strings to 4000 characters
> ----------------------------------------------------
>
> Key: TEIID-5135
> URL: https://issues.jboss.org/browse/TEIID-5135
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Minor
>
> Probably it's not bug. When running the following queries:
> {code:sql}
> Select Length(Repeat('abcde', 9000));; /* 4000 chars */
> Select Length(Repeat('a', 9000));; /* 4000 chars */
> {code}
> Teiid returns 4000 instead of 9000. Can the internal truncation be avoided (maybe in some cases) or not?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months