[JBoss JIRA] (TEIID-4897) Null pointer on ExecutionContext.getSubject().getPrincipals()
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4897?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4897:
---------------------------------------
The subject is expected to not be null as long as you are using a security domain.
If you are really on 8.11, you'll need to reproduce the issue in a later version - and clarify what the user (is it from a jdbc/odbc/web client) and source query (is it part of the main query plan or part of a materialized view load) are doing.
> Null pointer on ExecutionContext.getSubject().getPrincipals()
> -------------------------------------------------------------
>
> Key: TEIID-4897
> URL: https://issues.jboss.org/browse/TEIID-4897
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.11
> Reporter: Rafael Coutinho
> Assignee: Steven Hawkins
> Priority: Minor
>
> Is there any configuration that would avoid my translator to get the user logged into the TEIID connection?
> I'm extending the jdbc connector and during a query i want to get the currently logged user as displayed below.
> However I always get null for getSubject.
> @Override
> public ResultSetExecution createResultSetExecution(QueryExpression command, ExecutionContext executionContext, RuntimeMetadata metadata, Connection conn) throws TranslatorException {
> try {
> System.out.println(executionContext.getSubject());
> System.out.println(executionContext.getSubject().getPrincipals());
> } catch (Exception e) {
> System.err.println(e.getMessage());
> }
> return new SagenceIonicTranslatorExecution(command, conn, executionContext, this);
> }
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIID-4899) import foreign schema "import qualifiers" problem
by Bram Gadeyne (JIRA)
[ https://issues.jboss.org/browse/TEIID-4899?page=com.atlassian.jira.plugin... ]
Bram Gadeyne commented on TEIID-4899:
-------------------------------------
In the mean time I could import the required schema using the following syntax. But I'm not sure why the LIMIT TO and EXCEPT options didn't work.
{code:sql}
IMPORT FOREIGN SCHEMA GLIMS
FROM SERVER glims
INTO glims
OPTIONS(
importer.schemaPattern 'GLIMS',
importer.useFullSchemaName false,
importer.tableTypes 'TABLE,VIEW'
);
{code}
> import foreign schema "import qualifiers" problem
> -------------------------------------------------
>
> Key: TEIID-4899
> URL: https://issues.jboss.org/browse/TEIID-4899
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.3
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
>
> Hi I'm trying to import a schema but I get an error
> {code:sql}
> IMPORT FOREIGN SCHEMA GLIMS
> FROM SERVER glims
> INTO glims
> OPTIONS(
> importer.useFullSchemaName false,
> importer.tableTypes 'TABLE,VIEW'
> );
> {code}
> This results in an error:
> 09:57:34,782 ERROR [org.teiid.RUNTIME] (Worker6) TEIID30021 Uncaught exception processing work: org.teiid.metadata.ParseException: TEIID31259 In the
> statement ending with token ) on line 45 column 1 the ddl is not valid: TEIID60013 Duplicate Table TOAD_PLAN_TABLE
> at org.teiid.query.parser.QueryParser.parseDDL(QueryParser.java:567)
> at org.teiid.runtime.AbstractVDBDeployer.processVDBDDL(AbstractVDBDeployer.java:358)
> at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:262)
> at org.teiid.jboss.VDBService.access$1000(VDBService.java:82)
> at org.teiid.jboss.VDBService$6.run(VDBService.java:362)
> at org.teiid.jboss.VDBService$7.run(VDBService.java:392)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table TOAD_PLAN_TABLE
> at org.teiid.metadata.Schema.addTable(Schema.java:51)
> at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69)
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62)
> at org.teiid.metadata.MetadataRepository.loadMetadata(MetadataRepository.java:46)
> at org.teiid.runtime.AbstractVDBDeployer$MetadataRepositoryWrapper.loadMetadata(AbstractVDBDeployer.java:85)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.runtime.AbstractVDBDeployer$2.importSchema(AbstractVDBDeployer.java:334)
> at org.teiid.query.parser.SQLParser.importSchema(SQLParser.java:15411)
> at org.teiid.query.parser.SQLParser.ddlStmt(SQLParser.java:12641)
> at org.teiid.query.parser.SQLParser.parseMetadata(SQLParser.java:12577)
> at org.teiid.query.parser.QueryParser.parseDDL(QueryParser.java:561)
> ... 11 more
> Changing the import statement to only the desired tables results in the same error.
> {code:sql}
> IMPORT FOREIGN SCHEMA GLIMS
> LIMIT TO (LABANALYSE,LABANALYSECODE,LABANALYSESERIZIVCODE,LABERROR,LABFMD2ARTS,LABORDER,LABORDER2PRINT,LABPAT,LABPAT2ORDER,LABPRINTERCONFIG, LABPRINTERCONFIG_BACKUP,LABSPECIMEN,LABTITEL)
> FROM SERVER glims
> INTO glims
> OPTIONS(
> importer.useFullSchemaName false,
> importer.tableTypes 'TABLE,VIEW'
> );
> {code}
> Now explicitly stating that this TOAD_PLAN_TABLE should be ignored:
> {code:sql}
> IMPORT FOREIGN SCHEMA GLIMS
> EXCEPT (TOAD_PLAN_TABLE)
> FROM SERVER glims
> INTO glims
> OPTIONS(
> importer.useFullSchemaName false,
> importer.tableTypes 'TABLE,VIEW'
> );
> {code}
> results in:
> [standalone@localhost:9990 /] deploy D:\workspaceTeiid\IZ\vdb4-vdb.ddl
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jbos
> s.deployment.unit.\"vdb4-vdb.ddl\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"vdb4-vdb.ddl\".PARSE: WFLYSRV015
> 3: Failed to process phase PARSE of deployment \"vdb4-vdb.ddl\"
> Caused by: org.teiid.metadata.ParseException: TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered
> \"FOREIGN SCHEMA GLIMS [*]EXCEPT[*] (TOAD_PLAN_TABLE\" at line 40, column 9.
> Was expecting: \"from\" | \"limit\" | \"(\"
> Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered \"FOREIGN SCHEMA GLIMS [*]EXCEPT[*] (TOAD_PLA
> N_TABLE\" at line 40, column 9.
> Was expecting: \"from\" | \"limit\" | \"(\""},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"vdb4-vdb.ddl\".PAR
> SE"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}}}
> Also a small note about the docs:
> In the [example|https://teiid.gitbooks.io/documents/content/v/9.2.x/reference/ddl_deployment_mode.html#import_schema] "LIMIT TO customers, orders" should be "LIMIT TO (customers, orders)".
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIID-4899) import foreign schema "import qualifiers" problem
by Bram Gadeyne (JIRA)
Bram Gadeyne created TEIID-4899:
-----------------------------------
Summary: import foreign schema "import qualifiers" problem
Key: TEIID-4899
URL: https://issues.jboss.org/browse/TEIID-4899
Project: Teiid
Issue Type: Bug
Affects Versions: 9.3
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
Hi I'm trying to import a schema but I get an error
{code:sql}
IMPORT FOREIGN SCHEMA GLIMS
FROM SERVER glims
INTO glims
OPTIONS(
importer.useFullSchemaName false,
importer.tableTypes 'TABLE,VIEW'
);
{code}
This results in an error:
09:57:34,782 ERROR [org.teiid.RUNTIME] (Worker6) TEIID30021 Uncaught exception processing work: org.teiid.metadata.ParseException: TEIID31259 In the
statement ending with token ) on line 45 column 1 the ddl is not valid: TEIID60013 Duplicate Table TOAD_PLAN_TABLE
at org.teiid.query.parser.QueryParser.parseDDL(QueryParser.java:567)
at org.teiid.runtime.AbstractVDBDeployer.processVDBDDL(AbstractVDBDeployer.java:358)
at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:262)
at org.teiid.jboss.VDBService.access$1000(VDBService.java:82)
at org.teiid.jboss.VDBService$6.run(VDBService.java:362)
at org.teiid.jboss.VDBService$7.run(VDBService.java:392)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table TOAD_PLAN_TABLE
at org.teiid.metadata.Schema.addTable(Schema.java:51)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179)
at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368)
at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351)
at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324)
at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166)
at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306)
at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69)
at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96)
at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62)
at org.teiid.metadata.MetadataRepository.loadMetadata(MetadataRepository.java:46)
at org.teiid.runtime.AbstractVDBDeployer$MetadataRepositoryWrapper.loadMetadata(AbstractVDBDeployer.java:85)
at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
at org.teiid.runtime.AbstractVDBDeployer$2.importSchema(AbstractVDBDeployer.java:334)
at org.teiid.query.parser.SQLParser.importSchema(SQLParser.java:15411)
at org.teiid.query.parser.SQLParser.ddlStmt(SQLParser.java:12641)
at org.teiid.query.parser.SQLParser.parseMetadata(SQLParser.java:12577)
at org.teiid.query.parser.QueryParser.parseDDL(QueryParser.java:561)
... 11 more
Changing the import statement to only the desired tables results in the same error.
{code:sql}
IMPORT FOREIGN SCHEMA GLIMS
LIMIT TO (LABANALYSE,LABANALYSECODE,LABANALYSESERIZIVCODE,LABERROR,LABFMD2ARTS,LABORDER,LABORDER2PRINT,LABPAT,LABPAT2ORDER,LABPRINTERCONFIG, LABPRINTERCONFIG_BACKUP,LABSPECIMEN,LABTITEL)
FROM SERVER glims
INTO glims
OPTIONS(
importer.useFullSchemaName false,
importer.tableTypes 'TABLE,VIEW'
);
{code}
Now explicitly stating that this TOAD_PLAN_TABLE should be ignored:
{code:sql}
IMPORT FOREIGN SCHEMA GLIMS
EXCEPT (TOAD_PLAN_TABLE)
FROM SERVER glims
INTO glims
OPTIONS(
importer.useFullSchemaName false,
importer.tableTypes 'TABLE,VIEW'
);
{code}
results in:
[standalone@localhost:9990 /] deploy D:\workspaceTeiid\IZ\vdb4-vdb.ddl
{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jbos
s.deployment.unit.\"vdb4-vdb.ddl\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"vdb4-vdb.ddl\".PARSE: WFLYSRV015
3: Failed to process phase PARSE of deployment \"vdb4-vdb.ddl\"
Caused by: org.teiid.metadata.ParseException: TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered
\"FOREIGN SCHEMA GLIMS [*]EXCEPT[*] (TOAD_PLAN_TABLE\" at line 40, column 9.
Was expecting: \"from\" | \"limit\" | \"(\"
Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered \"FOREIGN SCHEMA GLIMS [*]EXCEPT[*] (TOAD_PLA
N_TABLE\" at line 40, column 9.
Was expecting: \"from\" | \"limit\" | \"(\""},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"vdb4-vdb.ddl\".PAR
SE"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}}}
Also a small note about the docs:
In the [example|https://teiid.gitbooks.io/documents/content/v/9.2.x/reference/ddl_deployment_mode.html#import_schema] "LIMIT TO customers, orders" should be "LIMIT TO (customers, orders)".
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIID-4894) Remove xml document models
by Bram Gadeyne (JIRA)
[ https://issues.jboss.org/browse/TEIID-4894?page=com.atlassian.jira.plugin... ]
Bram Gadeyne commented on TEIID-4894:
-------------------------------------
Hi,
Does this mean that all *.xmi models should be converted to DDL to work with version 10?
With tooling support I assume you mean that Teiiddesigner will also revert to DDL?
> Remove xml document models
> --------------------------
>
> Key: TEIID-4894
> URL: https://issues.jboss.org/browse/TEIID-4894
> Project: Teiid
> Issue Type: Task
> Components: Documentation, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> XML document models have been deprecated for a full release and are not expected to have tooling support in any future UI. Support should be removed from the server side.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIID-4895) Determine community requirements for WildFly usage
by Bram Gadeyne (JIRA)
[ https://issues.jboss.org/browse/TEIID-4895?page=com.atlassian.jira.plugin... ]
Bram Gadeyne commented on TEIID-4895:
-------------------------------------
Hi,
For us options 1 and 2 are currently the most relevant. We're running Teiid on a standalone Wildfly server.
> Determine community requirements for WildFly usage
> --------------------------------------------------
>
> Key: TEIID-4895
> URL: https://issues.jboss.org/browse/TEIID-4895
> Project: Teiid
> Issue Type: Task
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> WildFly is typically the runtime for Teiid. However we want feedback from the community on what style of WildFly integration is important:
> - The ability to deploy Teiid into a managed WildFly instance/cluster
> - The combination Teiid/WildFly artifact
> - A layered docker image
> - Not full WildFly, just Swarm
> - Not needed, just Embedded
> Based upon this we can better tune our documentation, downloads, and examples.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIID-4863) Run teiid embedded via Wildfly Swarm and Spring Boot
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4863?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-4863:
------------------------------------
Thanks for your comments, I don't have the answer for most of questions, but these questions can be the requirements for my research and investigation, for now, I work on make up a feasible task list, which like we did in supporting wildfly-swarm, once I got one, we can discuss it on a meeting, the start the developing work.
For why WildFly Swarm relation here? my initial thoughts is if add a fraction base on simple pojo(EmbeddedConfiguration), it more simply, do not depend on config-api.
> Run teiid embedded via Wildfly Swarm and Spring Boot
> ----------------------------------------------------
>
> Key: TEIID-4863
> URL: https://issues.jboss.org/browse/TEIID-4863
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Affects Versions: 10.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 10.0
>
>
> WildFly Swarm can use simple pojo to integrate framework, which compatible with EmbeddedConfiguration, actually this is encouraged way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months