June 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4903) Create a new server quickstart for the new infinispan hotrod connector/translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4903?page=com.atlassian.jira.plugin... ] Work on TEIID-4903 stopped by Van Halbert. ------------------------------------------ > Create a new server quickstart for the new infinispan hotrod connector/translator > --------------------------------------------------------------------------------- > > Key: TEIID-4903 > URL: https://issues.jboss.org/browse/TEIID-4903 > Project: Teiid > Issue Type: Task > Components: Infinispan, Quick Starts > Affects Versions: 9.3.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 8.12.x-6.4 > > > Create a new server quickstart for the new infinispan hotrod connector/translator. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4891) Fix and cleanup JDG quickstarts

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4891?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4891: ------------------------------- Fix Version/s: 8.12.x-6.4 > Fix and cleanup JDG quickstarts > ------------------------------- > > Key: TEIID-4891 > URL: https://issues.jboss.org/browse/TEIID-4891 > Project: Teiid > Issue Type: Task > Components: JDG Connector, Quick Starts > Affects Versions: 9.3, 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.x-6.4 > > > Fix and clean up the JDG related quickstarts that include: > - update instructions > - update CLI scripts > - update vdb's > - update module dependencies -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4971) Infinispan Hotrod can't access remote instance

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4971?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4971: ------------------------------- Component/s: Infinispan > Infinispan Hotrod can't access remote instance > ---------------------------------------------- > > Key: TEIID-4971 > URL: https://issues.jboss.org/browse/TEIID-4971 > Project: Teiid > Issue Type: Bug > Components: Infinispan, JDG Connector > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Blocker > > The Infinispan Hotrod connector writes to jdg's internal cache, which can't be accessed from remote hosts if the cache container is not secured and the user accessing the internal cache doesn't have specific privileges. > User can't authenticate via resource-adapter currently, enhancement TEIID-4904 is needed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4971) Infinispan Hotrod can't access remote instance

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-4971?page=com.atlassian.jira.plugin... ] Jan Stastny commented on TEIID-4971: ------------------------------------ Feel free to handle this issue as you are used to. What I wanted to achieve was to track the defect accordingly, not in a comment of an existing enhancement. One more thing that might be considered though is documenting the roles and privileges required to access the internal cache on remote instance. > Infinispan Hotrod can't access remote instance > ---------------------------------------------- > > Key: TEIID-4971 > URL: https://issues.jboss.org/browse/TEIID-4971 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Blocker > > The Infinispan Hotrod connector writes to jdg's internal cache, which can't be accessed from remote hosts if the cache container is not secured and the user accessing the internal cache doesn't have specific privileges. > User can't authenticate via resource-adapter currently, enhancement TEIID-4904 is needed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4904) Add support for identify security to the infinispan connector

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4904?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4904: ------------------------------------- That is right, that is what I saw how it is being used in Infinispan. I will document these options. > Add support for identify security to the infinispan connector > ------------------------------------------------------------- > > Key: TEIID-4904 > URL: https://issues.jboss.org/browse/TEIID-4904 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 10.0, 8.12.x-6.4 > > > Add support for identify secuirty to the new infinispan connector/translator. This is needed for openshift. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4904) Add support for identify security to the infinispan connector

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4904?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-4904 at 6/29/17 10:50 PM: -------------------------------------------------------------- For using UserName/Password use SaslMechanism = "CRAM-MD5", "DIGEST-MD5", "PLAIN" SaslMechanism = "EXTERNAL" indicates to use Keystore/Trustore was (Author: van.halbert): Valid SaslMechanism = "CRAM-MD5", "DIGEST-MD5", "PLAIN" > Add support for identify security to the infinispan connector > ------------------------------------------------------------- > > Key: TEIID-4904 > URL: https://issues.jboss.org/browse/TEIID-4904 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 10.0, 8.12.x-6.4 > > > Add support for identify secuirty to the new infinispan connector/translator. This is needed for openshift. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4904) Add support for identify security to the infinispan connector

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4904?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4904: ------------------------------------ Valid SaslMechanism = "CRAM-MD5", "DIGEST-MD5", "PLAIN" > Add support for identify security to the infinispan connector > ------------------------------------------------------------- > > Key: TEIID-4904 > URL: https://issues.jboss.org/browse/TEIID-4904 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 10.0, 8.12.x-6.4 > > > Add support for identify secuirty to the new infinispan connector/translator. This is needed for openshift. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4976) criteria duplicated when criteria includes the same columns as dependent join criteria

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4976?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4976: --------------------------------------- Are you asking to track down the original issue, or just to document that the issue existed on the given version? > criteria duplicated when criteria includes the same columns as dependent join criteria > -------------------------------------------------------------------------------------- > > Key: TEIID-4976 > URL: https://issues.jboss.org/browse/TEIID-4976 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.11.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Submitting a query that uses the same column for the join condition and criteria results in the criteria being duplicated on the dependent side of the join. > For example: > SELECT * FROM A, B > WHERE B.id = A.id AND A.id IN ('1','2','3') OPTION MAKEDEP B; > Results in the dependent side query looking like: > SELECT ... FROM B WHERE B.id IN ('1','2','3') AND B.id IN ('1','2','3'); > This looks to have already been resolved in later versions, but I was not able to find the original JIRA that would have addressed this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4966) Infinite loop when deploying a malformed vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4966?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4966. ----------------------------------- Resolution: Won't Fix Marking as won't fix. It's not immediately clear that our code is doing anything wrong, so this could be pursued with WildFly. > Infinite loop when deploying a malformed vdb > --------------------------------------------- > > Key: TEIID-4966 > URL: https://issues.jboss.org/browse/TEIID-4966 > Project: Teiid > Issue Type: Bug > Environment: * WildFly 10 > * Teiid Server 9.3.0 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > > Deploy a malformed vdb. Example with closing comment (--) but without a open comment (!--). > The following error start to appear in logs without end. > Deploying a correctly formed VDB after does not fix the problem. > Log extract; > 2017-06-22 17:46:48,971 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0035: Scan found countryServiceList-vdb.xml which is not well-formed at lineNumber: 3591, columnNumber: 9. Either the file was incompletely copied at the time of the scanning or it is just wrong. > ..... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4966) Infinite loop when deploying a malformed vdb

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4966?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4966: ------------------------------------- [~shawkins] not worth any time IMO > Infinite loop when deploying a malformed vdb > --------------------------------------------- > > Key: TEIID-4966 > URL: https://issues.jboss.org/browse/TEIID-4966 > Project: Teiid > Issue Type: Bug > Environment: * WildFly 10 > * Teiid Server 9.3.0 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > > Deploy a malformed vdb. Example with closing comment (--) but without a open comment (!--). > The following error start to appear in logs without end. > Deploying a correctly formed VDB after does not fix the problem. > Log extract; > 2017-06-22 17:46:48,971 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0035: Scan found countryServiceList-vdb.xml which is not well-formed at lineNumber: 3591, columnNumber: 9. Either the file was incompletely copied at the time of the scanning or it is just wrong. > ..... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2017