[JBoss JIRA] (TEIID-3044) Add function metadata to system tables / databasemetadata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3044?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3044:
---------------------------------------
The next issue we have is that the FunctionParameter class was never made to be a proper metadata object, so it's rather incomplete as to the metadata (especially the type information). This is a hold over from the old function logic. So we'll likely want to expand the FunctionParamter api and correct any version differences as part of the metadata validation process.
> Add function metadata to system tables / databasemetadata
> ---------------------------------------------------------
>
> Key: TEIID-3044
> URL: https://issues.jboss.org/browse/TEIID-3044
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JDBC Driver, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> We should expose source/system/udf functions via system metadata.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3075) OSGi bundle versions hardcoded
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3075?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3075:
-------------------------------------
The above mentioned ones are in commented blocks, there were bigger dependency issues in resolving all the dependencies with those.
> OSGi bundle versions hardcoded
> ------------------------------
>
> Key: TEIID-3075
> URL: https://issues.jboss.org/browse/TEIID-3075
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build/Kits
> Affects Versions: 8.7.1
> Reporter: Julian Coleman
> Assignee: Ramesh Reddy
> Priority: Minor
>
> The file:
> build/kits/karaf/teiid-karaf-features.xml
> contains hard-coded versions of some dependencies. For example:
> <bundle>wrap:mvn:org.apache.lucene/lucene-core/3.6.2</bundle>
> <bundle>mvn:org.infinispan/infinispan-query/5.2.1.Final</bundle>
> These should be replaced by the appropriate properties.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIID-3079) Security domain associated with data source is not getting deleted while deleting the data source, post server restart.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3079?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3079.
---------------------------------
Labels: Alpha2 (was: )
Fix Version/s: 8.7.1
8.9
Resolution: Done
Since VDB based security domain can not be determined at the start up time, there was dependency on set up on all the security domains. Changed this dependency to OPTIONAL, if in case VDB security domain deleted then it will end up in exception during the authentication.
> Security domain associated with data source is not getting deleted while deleting the data source,post server restart.
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3079
> URL: https://issues.jboss.org/browse/TEIID-3079
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7
> Reporter: Haifen Bi
> Assignee: Ramesh Reddy
> Labels: Alpha2
> Fix For: 8.7.1, 8.9
>
>
> We are migrating from Teiid 8.4 final to teiid 8.7 final.
> We have custom security domain for our data sources.
> We use JBoss DMR api to delete the datasource and the security domain while deleting a data source.
> With Teiid 8.4 this was working fine and both the datasource and the custom security domain used to get deleted , but with teiid 8.7 it gives following exception:
>
> {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "JBAS014762: Removing services has lead to unsatisfied dependencies: Service jboss.security.security-domain.edmsqlSecurityDomain was depended upon by service jboss.teiid.transport.embedded, service jboss.teiid.transport.jdbc, service jboss.teiid.transport.odbc"}}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIID-3079) Security domain associated with data source is not getting deleted while deleting the data source, post server restart.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3079?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-3079:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Security domain associated with data source is not getting deleted while deleting the data source,post server restart.
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3079
> URL: https://issues.jboss.org/browse/TEIID-3079
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7
> Reporter: Haifen Bi
> Assignee: Ramesh Reddy
>
> We are migrating from Teiid 8.4 final to teiid 8.7 final.
> We have custom security domain for our data sources.
> We use JBoss DMR api to delete the datasource and the security domain while deleting a data source.
> With Teiid 8.4 this was working fine and both the datasource and the custom security domain used to get deleted , but with teiid 8.7 it gives following exception:
>
> {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "JBAS014762: Removing services has lead to unsatisfied dependencies: Service jboss.security.security-domain.edmsqlSecurityDomain was depended upon by service jboss.teiid.transport.embedded, service jboss.teiid.transport.jdbc, service jboss.teiid.transport.odbc"}}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIID-3079) Security domain associated with data source is not getting deleted while deleting the data source, post server restart.
by Haifen Bi (JIRA)
Haifen Bi created TEIID-3079:
--------------------------------
Summary: Security domain associated with data source is not getting deleted while deleting the data source,post server restart.
Key: TEIID-3079
URL: https://issues.jboss.org/browse/TEIID-3079
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 8.7
Reporter: Haifen Bi
Assignee: Steven Hawkins
We are migrating from Teiid 8.4 final to teiid 8.7 final.
We have custom security domain for our data sources.
We use JBoss DMR api to delete the datasource and the security domain while deleting a data source.
With Teiid 8.4 this was working fine and both the datasource and the custom security domain used to get deleted , but with teiid 8.7 it gives following exception:
{"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "JBAS014762: Removing services has lead to unsatisfied dependencies: Service jboss.security.security-domain.edmsqlSecurityDomain was depended upon by service jboss.teiid.transport.embedded, service jboss.teiid.transport.jdbc, service jboss.teiid.transport.odbc"}}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIID-3077) SOLR: Type date should be converted into Timestamp
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3077?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3077.
-----------------------------------
Fix Version/s: 8.7.1
8.9
Resolution: Done
changed the type mapping to timestamp
> SOLR: Type date should be converted into Timestamp
> --------------------------------------------------
>
> Key: TEIID-3077
> URL: https://issues.jboss.org/browse/TEIID-3077
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Filip Elias
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.9
>
>
> SOLR translator converts solr's date type into java.sql.Date, but SOLR's date format is rather timestamp[1]. When the solr's date is converted into java.sql.Date, the information about hours,minutes and seconds will be lost.
> [1] "TimestampValue": "1999-12-31T23:00:00Z",
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months