[JBoss JIRA] (TEIID-3504) Null pointer exception executing dynamic sql
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3504:
-------------------------------------
Summary: Null pointer exception executing dynamic sql
Key: TEIID-3504
URL: https://issues.jboss.org/browse/TEIID-3504
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.11
When a procedure with dynamic sql is rerun the cloning of the group context allows for the same linked list to be modified by multiple threads leading to errors, which typically resemble a null pointer exception (for example at QueryResolver line 259 due to a null group). The cloning also allows for the group context groups to grow in number as the locally scoped groups are re-added.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TEIID-3475) Add a separate example module for embedded examples
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3475?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3475:
-------------------------------------
Yea, there is no reason to include every possible example in kit. Original intent was to keep something simple inline for quick reference, now that we got various full-fledged examples, we certainly need to document their usage dependencies etc to match the expectations. We can't certainly do that with current model. That is same route we took for main line too.
> Add a separate example module for embedded examples
> ----------------------------------------------------
>
> Key: TEIID-3475
> URL: https://issues.jboss.org/browse/TEIID-3475
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Affects Versions: 8.11
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 8.11
>
> Attachments: drools-examples.png
>
>
> Add a separate example module for embedded examples, it will contain a runnable jar, which will load all available examples, it will also contain transaction manager, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TEIID-3499) IllegalStateException wihle using DataNotAvailableException.NO_POLLING
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3499?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3499:
----------------------------------
Issue Type: Bug (was: Feature Request)
Regardless this is not expected for the client. Is is possible that you have a multi-threaded client using the same connection?
> IllegalStateException wihle using DataNotAvailableException.NO_POLLING
> ----------------------------------------------------------------------
>
> Key: TEIID-3499
> URL: https://issues.jboss.org/browse/TEIID-3499
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.11
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
>
> java.lang.IllegalStateException: Must be in MORE_WORK
> at org.teiid.dqp.internal.process.AbstractWorkItem.startProcessing(AbstractWorkItem.java:70)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:48)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:298)
> at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173)
> at com.sun.proxy.$Proxy14.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:661)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:527)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261)
> at com.ca.apm.server.teiid.REPL.printQuery(REPL.java:90)
> at com.ca.apm.server.teiid.REPL.printQuery(REPL.java:116)
> at com.ca.apm.server.teiid.REPL.issue62_no_timerangekey(REPL.java:713)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TEIID-3500) execute SYSADMIN.matViewStatus failed cause infinite loop in MaterializationManager JobSchedular
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3500?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3500.
-----------------------------------
Resolution: Rejected
A myql long type is a long text, which imports as a clob. The type would need to be bigint.
> execute SYSADMIN.matViewStatus failed cause infinite loop in MaterializationManager JobSchedular
> ------------------------------------------------------------------------------------------------
>
> Key: TEIID-3500
> URL: https://issues.jboss.org/browse/TEIID-3500
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.11
> Reporter: Kylin Soong
> Attachments: ExternalMaterializationMysql.java, mat-mysql-vdb-debug.xml, mat-mysql-vdb.xml, schema.sql
>
>
> While using Mysql, SYSADMIN.matViewStatus throw a SQLExecption
> ~~~
> java.sql.SQLException: org.teiid.api.exception.query.QueryProcessingException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE (('SELECT TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality, LoadNumber, VARIABLES.action FROM ' || VARIABLES.statusTable) || crit) AS TargetSchemaName string, TargetName string, Valid boolean, LoadState string, Updated timestamp, Cardinality long, LoadNumber long, OnErrorAction string USING vdbName = VARIABLES.vdbName, vdbVersion = VARIABLES.vdbVersion, schemaName = matViewStatus.schemaName, viewName = matViewStatus.viewName" with the SQL statement "(('SELECT TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality, LoadNumber, VARIABLES.action FROM ' || VARIABLES.statusTable) || crit)" due to: The datatype 'clob' for element 'Cardinality' in the dynamic SQL cannot be implicitly converted to 'long'.
> ~~~
> this cause scheduleJob infinite loop, 'SYSADMIN.loadMatView' never be executed.
> If we didn't configure 'teiid_rel:MATVIEW_TTL', execute SYSADMIN.matViewStatus manually , full stack trace as [1]
> If test with H2 database, SYSADMIN.matViewStatus works fine.
> [1] stack trace
> ~~~
> 2015-06-01 11:35 088 WARNING [org.teiid.PROCESSOR] (main) TEIID30020 Processing exception for request gQ25UW2DqodQ.7 'TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE (('SELECT TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality, LoadNumber, VARIABLES.action FROM ' || VARIABLES.statusTable) || crit) AS TargetSchemaName string, TargetName string, Valid boolean, LoadState string, Updated timestamp, Cardinality long, LoadNumber long, OnErrorAction string USING vdbName = VARIABLES.vdbName, vdbVersion = VARIABLES.vdbVersion, schemaName = matViewStatus.schemaName, viewName = matViewStatus.viewName" with the SQL statement "(('SELECT TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality, LoadNumber, VARIABLES.action FROM ' || VARIABLES.statusTable) || crit)" due to: The datatype 'clob' for element 'Cardinality' in the dynamic SQL cannot be implicitly converted to 'long'.'. Originally QueryProcessingException ExecDynamicSqlInstruction.java:341. Enable more detailed logging to see the entire stacktrace.
> org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE (('SELECT TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality, LoadNumber, VARIABLES.action FROM ' || VARIABLES.statusTable) || crit) AS TargetSchemaName string, TargetName string, Valid boolean, LoadState string, Updated timestamp, Cardinality long, LoadNumber long, OnErrorAction string USING vdbName = VARIABLES.vdbName, vdbVersion = VARIABLES.vdbVersion, schemaName = matViewStatus.schemaName, viewName = matViewStatus.viewName" with the SQL statement "(('SELECT TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality, LoadNumber, VARIABLES.action FROM ' || VARIABLES.statusTable) || crit)" due to: The datatype 'clob' for element 'Cardinality' in the dynamic SQL cannot be implicitly converted to 'long'.
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:694)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:64)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:533)
> at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:529)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:1062)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:314)
> at org.teiid.example.util.JDBCUtils.execute(JDBCUtils.java:86)
> at org.teiid.test.perf.ExternalMaterializationMysqlDebug.executeMatViewStatus(ExternalMaterializationMysqlDebug.java:83)
> at org.teiid.test.perf.ExternalMaterializationMysqlDebug.main(ExternalMaterializationMysqlDebug.java:65)
> Caused by: org.teiid.api.exception.query.QueryProcessingException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE (('SELECT TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality, LoadNumber, VARIABLES.action FROM ' || VARIABLES.statusTable) || crit) AS TargetSchemaName string, TargetName string, Valid boolean, LoadState string, Updated timestamp, Cardinality long, LoadNumber long, OnErrorAction string USING vdbName = VARIABLES.vdbName, vdbVersion = VARIABLES.vdbVersion, schemaName = matViewStatus.schemaName, viewName = matViewStatus.viewName" with the SQL statement "(('SELECT TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality, LoadNumber, VARIABLES.action FROM ' || VARIABLES.statusTable) || crit)" due to: The datatype 'clob' for element 'Cardinality' in the dynamic SQL cannot be implicitly converted to 'long'.
> at org.teiid.query.processor.proc.ExecDynamicSqlInstruction.process(ExecDynamicSqlInstruction.java:249)
> at org.teiid.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:384)
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatchDirect(ProcedurePlan.java:293)
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:267)
> at org.teiid.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:118)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:148)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:457)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:298)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173)
> at com.sun.proxy.$Proxy11.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:661)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:527)
> ... 5 more
> Caused by: org.teiid.api.exception.query.QueryProcessingException: The datatype 'clob' for element 'Cardinality' in the dynamic SQL cannot be implicitly converted to 'long'.
> at org.teiid.query.processor.proc.ExecDynamicSqlInstruction.validateDynamicCommand(ExecDynamicSqlInstruction.java:341)
> at org.teiid.query.processor.proc.ExecDynamicSqlInstruction.process(ExecDynamicSqlInstruction.java:168)
> ... 34 more
> ~~~
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TEIID-3475) Add a separate example module for embedded examples
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3475?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3475:
---------------------------------------
Ramesh are you thinking then that we won't bother kitting the examples? Just rely on users browsing and checking out from git?
> Add a separate example module for embedded examples
> ----------------------------------------------------
>
> Key: TEIID-3475
> URL: https://issues.jboss.org/browse/TEIID-3475
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Affects Versions: 8.11
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 8.11
>
> Attachments: drools-examples.png
>
>
> Add a separate example module for embedded examples, it will contain a runnable jar, which will load all available examples, it will also contain transaction manager, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TEIID-3351) Quick Start "dynamicvdb-datafederation" needlessly made complicated
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3351?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3351:
----------------------------------
Fix Version/s: 8.11
Component/s: Quick Starts
Putting into a release bucket to see if we can get this addressed.
> Quick Start "dynamicvdb-datafederation" needlessly made complicated
> -------------------------------------------------------------------
>
> Key: TEIID-3351
> URL: https://issues.jboss.org/browse/TEIID-3351
> Project: Teiid
> Issue Type: Quality Risk
> Components: Quick Starts
> Reporter: Ramesh Reddy
> Assignee: Van Halbert
> Fix For: 8.11
>
>
> The "dynamicvdb-datafederation" example in the Quick Starts example is needlessly made complicated. Originally this is designed to have one File and RDBMS source, to show a simple data integration through Teiid.
> Now, it has
> - Excel integration
> - Materialization Example
> - more models
> I am not opposed to having these features shown in an example, however not in this example. This needs to be as simple as possible to show a quick introduction to the Teiid. Please move these into separate quick starts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TEIID-3503) Use of ModelMetaData required teiid-admin jar
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3503?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3503:
---------------------------------------
> Any devs using teiid need access to this earlyrelease repo.
That is correct and is what I was referring to in the previous comment. The central issue is that for practical purposes it's best to keep our project aligned with the our product mainline, which targets current EAP releases. Since JBoss/Red Hat wants to further delineate projects and product there is no corresponding community release to match the later EAP releases. The closest are the EAP alphas. As you can see however there are some issues with the model and layered community projects.
> Either create like "admin-jboss-integration" or move to "jboss-integration" module.
You'd probably need a new module to keep the adminshell from picking up the jboss-integration dependencies.
> Use of ModelMetaData required teiid-admin jar
> ---------------------------------------------
>
> Key: TEIID-3503
> URL: https://issues.jboss.org/browse/TEIID-3503
> Project: Teiid
> Issue Type: Quality Risk
> Components: Embedded
> Affects Versions: 8.10
> Reporter: Michael Davies
> Assignee: Ramesh Reddy
> Priority: Minor
>
> We are using Embedded and specifically ModelMetaData, for specifying VDB.
> ModelMetaData class comes from teiid-admin project, which pulls in a lot of AS dependencies, some of which are only available from earlyrelease maven repo.
> For example - org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4
> So essentially users developing against released teiid API (using ModelMetaData) now have dependency on earlyaccess repo.
> Where I work the people who manage the internal company repo do not like proxying non-release repos, and so this causes a bit of a pain.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TEIID-3503) Use of ModelMetaData required teiid-admin jar
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3503?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3503:
-------------------------------------
I think we need to move away the JBoss EAP specific dependencies from this module to be portable. Either create like "admin-jboss-integration" or move to "jboss-integration" module.
> Use of ModelMetaData required teiid-admin jar
> ---------------------------------------------
>
> Key: TEIID-3503
> URL: https://issues.jboss.org/browse/TEIID-3503
> Project: Teiid
> Issue Type: Quality Risk
> Components: Embedded
> Affects Versions: 8.10
> Reporter: Michael Davies
> Assignee: Ramesh Reddy
> Priority: Minor
>
> We are using Embedded and specifically ModelMetaData, for specifying VDB.
> ModelMetaData class comes from teiid-admin project, which pulls in a lot of AS dependencies, some of which are only available from earlyrelease maven repo.
> For example - org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4
> So essentially users developing against released teiid API (using ModelMetaData) now have dependency on earlyaccess repo.
> Where I work the people who manage the internal company repo do not like proxying non-release repos, and so this causes a bit of a pain.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TEIID-3503) Use of ModelMetaData required teiid-admin jar
by Michael Davies (JIRA)
[ https://issues.jboss.org/browse/TEIID-3503?page=com.atlassian.jira.plugin... ]
Michael Davies edited comment on TEIID-3503 at 6/1/15 11:27 AM:
----------------------------------------------------------------
teiid-parent-8.10.0.Final pom depends upon
<version.org.jboss.as>7.4.0.Final-redhat-4</version.org.jboss.as>
Now as far as I can see 7.4.0.Final-redhat-4 is available on here only
<id>jboss-earlyaccess</id>
<name>JBoss Early Access</name>
<url>https://maven.repository.redhat.com/earlyaccess/all/</url>
So this is not restricted to developers using embedded. Any devs using teiid need access to this earlyrelease repo.
was (Author: mickalas):
teiid-parent-8.10.0.Final pom depends upon
<version.org.jboss.as>7.4.0.Final-redhat-4</version.org.jboss.as>
Now as far as I can see 7.4.0.Final-redhat-4 is available on here only
<id>jboss-earlyaccess</id>
<name>JBoss Early Access</name>
<url>https://maven.repository.redhat.com/earlyaccess/all/</url>
So this is not restricted to embedded users. Any devs using teiid need access to this earlyrelease repo.
> Use of ModelMetaData required teiid-admin jar
> ---------------------------------------------
>
> Key: TEIID-3503
> URL: https://issues.jboss.org/browse/TEIID-3503
> Project: Teiid
> Issue Type: Quality Risk
> Components: Embedded
> Affects Versions: 8.10
> Reporter: Michael Davies
> Assignee: Ramesh Reddy
> Priority: Minor
>
> We are using Embedded and specifically ModelMetaData, for specifying VDB.
> ModelMetaData class comes from teiid-admin project, which pulls in a lot of AS dependencies, some of which are only available from earlyrelease maven repo.
> For example - org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4
> So essentially users developing against released teiid API (using ModelMetaData) now have dependency on earlyaccess repo.
> Where I work the people who manage the internal company repo do not like proxying non-release repos, and so this causes a bit of a pain.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TEIID-3503) Use of ModelMetaData required teiid-admin jar
by Michael Davies (JIRA)
[ https://issues.jboss.org/browse/TEIID-3503?page=com.atlassian.jira.plugin... ]
Michael Davies commented on TEIID-3503:
---------------------------------------
teiid-parent-8.10.0.Final pom depends upon
<version.org.jboss.as>7.4.0.Final-redhat-4</version.org.jboss.as>
Now as far as I can see 7.4.0.Final-redhat-4 is available on here only
<id>jboss-earlyaccess</id>
<name>JBoss Early Access</name>
<url>https://maven.repository.redhat.com/earlyaccess/all/</url>
So this is not restricted to embedded users. Any devs using teiid need access to this earlyrelease repo.
> Use of ModelMetaData required teiid-admin jar
> ---------------------------------------------
>
> Key: TEIID-3503
> URL: https://issues.jboss.org/browse/TEIID-3503
> Project: Teiid
> Issue Type: Quality Risk
> Components: Embedded
> Affects Versions: 8.10
> Reporter: Michael Davies
> Assignee: Ramesh Reddy
> Priority: Minor
>
> We are using Embedded and specifically ModelMetaData, for specifying VDB.
> ModelMetaData class comes from teiid-admin project, which pulls in a lot of AS dependencies, some of which are only available from earlyrelease maven repo.
> For example - org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4
> So essentially users developing against released teiid API (using ModelMetaData) now have dependency on earlyaccess repo.
> Where I work the people who manage the internal company repo do not like proxying non-release repos, and so this causes a bit of a pain.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months