[JBoss JIRA] (TEIIDDES-2497) Incorrect "Name in Source" when importing from JDBC Database using Informix
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2497?page=com.atlassian.jira.plu... ]
Debbie Steigner reassigned TEIIDDES-2497:
-----------------------------------------
Assignee: Barry LaFond
> Incorrect "Name in Source" when importing from JDBC Database using Informix
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2497
> URL: https://issues.jboss.org/browse/TEIIDDES-2497
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Bruno Machado
> Assignee: Barry LaFond
> Labels: designer, informix, metadata, teiid
>
> When importing from JDBC Database using a Informix connection, an incorrect "Name in source" metadata is set as "catalog":"schema":"table-name" instead of "catalog":"schema"."table-name", the delimiter between schema and table-name is set to ':' but Informix uses '.'.
> The ':' character must be replaced by a '.' between schema and table name when importing informix tables using Import From JDBC Database.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2501) Modify dialogs that are deemed too large to use on lower-resolution screens
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2501:
--------------------------------------
Summary: Modify dialogs that are deemed too large to use on lower-resolution screens
Key: TEIIDDES-2501
URL: https://issues.jboss.org/browse/TEIIDDES-2501
Project: Teiid Designer
Issue Type: Bug
Components: Dialogs
Reporter: Barry LaFond
Several of Designer's dialogs and wizards are too large to successfully demo on lower-resolution screens. There's a request to modify some of these to reduce the size of the panels/dialogs. Some of this could involve adding scrolling of the outer panel. Others might require re-arranging widgets/sub-panels, adding tab'd panels, etc.
* Transformation's Reconciler Dialog
* Create Web Services dialog
* Salesforce Importer (maybe JDBC Importer)
* ... (TBD)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2497) Incorrect "Name in Source" when importing from JDBC Database using Informix
by Bruno Machado (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2497?page=com.atlassian.jira.plu... ]
Bruno Machado updated TEIIDDES-2497:
------------------------------------
Priority: Major (was: Minor)
> Incorrect "Name in Source" when importing from JDBC Database using Informix
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2497
> URL: https://issues.jboss.org/browse/TEIIDDES-2497
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Bruno Machado
> Labels: designer, informix, metadata, teiid
>
> When importing from JDBC Database using a Informix connection, an incorrect "Name in source" metadata is set as "catalog":"schema":"table-name" instead of "catalog":"schema"."table-name", the delimiter between schema and table-name is set to ':' but Informix uses '.'.
> The ':' character must be replaced by a '.' between schema and table name when importing informix tables using Import From JDBC Database.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2461) Allow using JBoss AS connection timeout property when trying to connect/find Teiid Server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2461?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2461:
----------------------------------------
The user provided the following info which describes how/where we can set this property. This would also require exposing this property in Designer as a preference
org.jboss.ide.eclipse.as.core.server.v7.management.AS7ManagementDetails class had a property constructor[2]. It would be available to set "IAS7ManagementDetails.PROPERTY_TIMEOUT" property. However, the org/teiid/designer/runtime/adapter/JBoss7ServerUtil.java[3] did not use its property constructor.
[1]
ex)
./jboss-cli.sh --controller=XXXXXX:9999 -c --user=admin --password=**** --timeout=10000
[2]
public class AS7ManagementDetails implements IServerProvider, IAS7ManagementDetails {
private IServer server;
private Map<String, Object> properties;
public AS7ManagementDetails(IServer server) {
this(server, new HashMap<String,Object>(0));
}
-> public AS7ManagementDetails(IServer server, Map<String, Object> props) {
this.server = server;
this.properties = props;
}
[3]
private static ModelNode executeRequest(IServer parentServer, JBoss7Server jboss7Server, ModelNode request) throws Exception {
String requestString = request.toJSONString(true);
String resultString = JBoss7ManagerUtil.getService(parentServer).execute(new AS7ManagementDetails(parentServer), requestString);
return ModelNode.fromJSONString(resultString);
}
> Allow using JBoss AS connection timeout property when trying to connect/find Teiid Server
> -----------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2461
> URL: https://issues.jboss.org/browse/TEIIDDES-2461
> Project: Teiid Designer
> Issue Type: Enhancement
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 9.1, 9.0.2
>
>
> The teiid-designer cannot connect to remote JDV server by timeout exceptions[1]. However, the teiid-designer cannnot set timeout for it.
> [1]
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:153)
> at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
> at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:127)
> at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.preLaunchCheck(StandardRSEStartLaunchDelegate.java:72)
> at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.preLaunchCheck(RSECommandLineLaunchController.java:103)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:325)
> ... 23 more
> Caused by: java.net.ConnectException: JBAS012144: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 25 more
> Additional information:
> We want to set a property of "IAS7ManagementDetails.PROPERTY_TIMEOUT" via teiid-designer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2500) Problems with model created via import from Salesforce when using JOIN query
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2500?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-2500:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1216954
> Problems with model created via import from Salesforce when using JOIN query
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-2500
> URL: https://issues.jboss.org/browse/TEIIDDES-2500
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Reporter: Matus Makovy
> Attachments: log, salesdynamic-vdb.xml, SalesforceTD.zip
>
>
> Discovered this issue when trying to verify TEIID-3112
> I am trying to execute this query on VDB created via import from SalesForce in Teiid Designer.
> {quote}
> select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".salesforce.Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".salesforce.Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> And I get this exception:
> {quote}
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: Invalid QName in mapping: sf:INVALID_TYPE
> {quote}
> Log attached
> With dynamic VDB created manually or with import using Teiid Connection Importer via Designer everything works.
> Project from Designer + dynamic VDB attached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2500) Problems with model created via import from Salesforce when using JOIN query
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2500?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2500:
-----------------------------------
Attachment: salesdynamic-vdb.xml
log
SalesforceTD.zip
log + dynamic VDB created manually + Salesforce project from TD attached
> Problems with model created via import from Salesforce when using JOIN query
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-2500
> URL: https://issues.jboss.org/browse/TEIIDDES-2500
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Reporter: Matus Makovy
> Attachments: log, salesdynamic-vdb.xml, SalesforceTD.zip
>
>
> Discovered this issue when trying to verify TEIID-3112
> I am trying to execute this query on VDB created via import from SalesForce in Teiid Designer.
> {quote}
> select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".salesforce.Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".salesforce.Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> And I get this exception:
> {quote}
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: Invalid QName in mapping: sf:INVALID_TYPE
> {quote}
> Log attached
> With dynamic VDB created manually or with import using Teiid Connection Importer via Designer everything works.
> Project from Designer + dynamic VDB attached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2500) Problems with model created via import from Salesforce when using JOIN query
by Matus Makovy (JIRA)
Matus Makovy created TEIIDDES-2500:
--------------------------------------
Summary: Problems with model created via import from Salesforce when using JOIN query
Key: TEIIDDES-2500
URL: https://issues.jboss.org/browse/TEIIDDES-2500
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 9.0.1
Reporter: Matus Makovy
Discovered this issue when trying to verify TEIID-3112
I am trying to execute this query on VDB created via import from SalesForce in Teiid Designer.
{quote}
select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".salesforce.Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".salesforce.Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
{quote}
And I get this exception:
{quote}
org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: Invalid QName in mapping: sf:INVALID_TYPE
{quote}
Log attached
With dynamic VDB created manually or with import using Teiid Connection Importer via Designer everything works.
Project from Designer + dynamic VDB attached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2499) Support modelling/mapping of ASN.1 compliant data
by Johnathon Lee (JIRA)
Johnathon Lee created TEIIDDES-2499:
---------------------------------------
Summary: Support modelling/mapping of ASN.1 compliant data
Key: TEIIDDES-2499
URL: https://issues.jboss.org/browse/TEIIDDES-2499
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Johnathon Lee
LDAP is based on x509 standards with an underlying and explicit data model mapping to ASN.1 which is what LDAP supports. ie: LDAP specific structures and syntax in the designer modelling environment, an LDAP metamodel.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2498) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator
by Bruno Machado (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2498?page=com.atlassian.jira.plu... ]
Bruno Machado updated TEIIDDES-2498:
------------------------------------
Labels: ddl designer informix schema teiid (was: )
> Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2498
> URL: https://issues.jboss.org/browse/TEIIDDES-2498
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Bruno Machado
> Labels: ddl, designer, informix, schema, teiid
>
> When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'.
> The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator.
> useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2498) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator
by Bruno Machado (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2498?page=com.atlassian.jira.plu... ]
Bruno Machado updated TEIIDDES-2498:
------------------------------------
Description:
When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'.
The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator.
useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog".
was:
When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'.
The '.' character must be replaced by a ':' between schema and table name when importing from Teiid Data Source Connection using Informix translator.
useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog".
> Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2498
> URL: https://issues.jboss.org/browse/TEIIDDES-2498
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Bruno Machado
>
> When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'.
> The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator.
> useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years