[JBoss JIRA] (TEIID-3001) Custom translator cannot control its own namespace prefix
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3001?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3001:
------------------------------------
what's the name of the utility? I think I missed that in the documentation.
> Custom translator cannot control its own namespace prefix
> ---------------------------------------------------------
>
> Key: TEIID-3001
> URL: https://issues.jboss.org/browse/TEIID-3001
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7.1, 8.8
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> When creating a custom translator, unable to control the namespace prefix:
> SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2014' AS n0
> it uses 'n0'.
> I think the reason is the DDLStringVisitor only references BUILTIN_PREFIXES, for which is loaded from MetadataFactory. So if your namespace isn't a built in, it ends up with 'n0'. And the DDLStringVisitor doesn't have a way to get the MetadataFactory.namespaces that are added by calling:
> metadataFactory.addNamespace(PREFIX, URI.substring(1, URI.length()-1));
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 7 months
[JBoss JIRA] (TEIID-3001) Custom translator cannot control its own namespace prefix
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3001?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3001.
-----------------------------------
Resolution: Rejected
For a custom translator there is little utility in having control over the prefix as well.
The intention behind "built-in" prefixes was so that users would not have to redeclare well-known namespaces nor use a lengthy uri directly.
> Custom translator cannot control its own namespace prefix
> ---------------------------------------------------------
>
> Key: TEIID-3001
> URL: https://issues.jboss.org/browse/TEIID-3001
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7.1, 8.8
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> When creating a custom translator, unable to control the namespace prefix:
> SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2014' AS n0
> it uses 'n0'.
> I think the reason is the DDLStringVisitor only references BUILTIN_PREFIXES, for which is loaded from MetadataFactory. So if your namespace isn't a built in, it ends up with 'n0'. And the DDLStringVisitor doesn't have a way to get the MetadataFactory.namespaces that are added by calling:
> metadataFactory.addNamespace(PREFIX, URI.substring(1, URI.length()-1));
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 7 months
[JBoss JIRA] (TEIID-3001) Custom translator cannot control its own namespace prefix
by Van Halbert (JIRA)
Van Halbert created TEIID-3001:
----------------------------------
Summary: Custom translator cannot control its own namespace prefix
Key: TEIID-3001
URL: https://issues.jboss.org/browse/TEIID-3001
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Misc. Connectors
Affects Versions: 8.7.1, 8.8
Reporter: Van Halbert
Assignee: Steven Hawkins
When creating a custom translator, unable to control the namespace prefix:
SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2014' AS n0
it uses 'n0'.
I think the reason is the DDLStringVisitor only references BUILTIN_PREFIXES, for which is loaded from MetadataFactory. So if your namespace isn't a built in, it ends up with 'n0'. And the DDLStringVisitor doesn't have a way to get the MetadataFactory.namespaces that are added by calling:
metadataFactory.addNamespace(PREFIX, URI.substring(1, URI.length()-1));
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 7 months
[JBoss JIRA] (TEIID-2881) Add support to use DSL when querying remote JDG 6.2
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2881?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2881:
---------------------------------------
Van, when I pull the commit I'm seeing some issues. It looks like we never included the translator/connector in the module list in the connectors pom. When I do that, there is a compile error with the translator. Do you want to me to attempt to address or do you want to have a look first?
> Add support to use DSL when querying remote JDG 6.2
> ---------------------------------------------------
>
> Key: TEIID-2881
> URL: https://issues.jboss.org/browse/TEIID-2881
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Add support for querying remote JDG 6.2 using DSL.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 7 months