[JBoss JIRA] (TEIIDDES-2721) message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." in a newer version of the designer
by Lukas Mro (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2721?page=com.atlassian.jira.plu... ]
Lukas Mro edited comment on TEIIDDES-2721 at 1/7/16 1:09 PM:
-------------------------------------------------------------
Thanks for fast answer
My Teiid version is 8.11.4 and current designer v. is 9.1.1 1933 B2 (ups ;) )
After update to 9.2 i get this info and i cant escape from it. It comes back all the time...
I was changing vdb version in vdb editor and saving this change was required, but it didn`t help.
:(
Even if i deleted all vdb`s and creates them from scratch the error comes back.
Even if name of vdb`s was different
was (Author: lukaszmro):
Thanks for fast answer
My Teiid version is 8.11.4 and current designer v. is 9.1.1 1933 B2 (ups ;) )
After update to 9.2 i get this info and i cant escape from it. It comes back all the time...
I was changing vdb version in vdb editor and saving this change was required, but it didn`t help.
:(
> message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." in a newer version of the designer
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2721
> URL: https://issues.jboss.org/browse/TEIIDDES-2721
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.2
> Reporter: Bram Gadeyne
>
> The designer gives me this error message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." The vdb however was created in version 9.1.1. and I'm using 9.2.0.
> Is there a possibility to "upgrade" a vdb to a newer version or see what is incompatible?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2721) message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." in a newer version of the designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2721?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2721:
----------------------------------------
[~lukaszmro] [~gadeyne.bram] Because Teiid Designer allows users to connect to a Teiid server versions different than Designer's supported current client version, this validation message was created. A VDB created against a Teiid 8.11 instance (Designer 9.2) may support properties that didn't exist in Teiid 8.7-8.10. (Designer 9.1). So if you are connected to an older server, that VDB may not deploy or the newer properties may have no affect at runtime.
Opening up the VDB Editor, and changing any property so you can save it will always re-validate against the current Default Teiid Instance as part of the save operation.
> message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." in a newer version of the designer
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2721
> URL: https://issues.jboss.org/browse/TEIIDDES-2721
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.2
> Reporter: Bram Gadeyne
>
> The designer gives me this error message "This VDB was created in a newer version of Designer hence may contain properties that are not compatible with this version." The vdb however was created in version 9.1.1. and I'm using 9.2.0.
> Is there a possibility to "upgrade" a vdb to a newer version or see what is incompatible?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2617) "Teiid Connection>>Source Model" fails for HBase Datasource
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2617?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2617:
-----------------------------------
Fix Version/s: 9.0.5
9.2.1
> "Teiid Connection>>Source Model" fails for HBase Datasource
> -----------------------------------------------------------
>
> Key: TEIIDDES-2617
> URL: https://issues.jboss.org/browse/TEIIDDES-2617
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.2
> Reporter: Debbie Steigner
> Fix For: 9.0.5, 9.2.1
>
>
> "Teiid Connection>>Source Model" fails for HBase Datasource. The JDBC importer works. Error in the server log:
> When trying to import into the Designer with Teiid Connection, it errors on the Importvdb metadata load with "ERROR 1101 (XCL01): ResultSet is closed.":
> 14:46:33,771 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "importVDB-vdb.xml" (runtime-name: "importVDB-vdb.xml")
> 14:46:33,825 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB importVDB.1 model "importVDBSrcModel" metadata is currently being loaded. Start Time: 8/4/15 2:46 PM
> 14:46:33,825 INFO [org.teiid.CONNECTOR] (teiid-async-threads - 1) HBaseExecutionFactory Commit=true;DatabaseProductName=Phoenix;DatabaseProductVersion=4.3;DriverMajorVersion=4;DriverMajorVersion=3;DriverName=PhoenixEmbeddedDriver;DriverVersion=4.3;IsolationLevel=2
> 14:46:33,951 INFO [org.jboss.as.server] (management-handler-thread - 8) JBAS015859: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml")
> 14:46:34,210 WARN [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: ERROR 1101 (XCL01): ResultSet is closed.
> 14:46:35,736 INFO [org.teiid.RUNTIME] (MSC service thread 1-7) TEIID50026 VDB "importVDB.1[importVDBSrcModel{importVDBSrcModel=importVDBSrcModel, hbase, java:/PhoenixDS}]" undeployed.
> Saw this https://developer.jboss.org/thread/260099, customer is getting the same winutils error and they state: This error usually comes when the hadoop server is accessed from windows machine.
> we get this error in other windows environment but this does not affect the application.
> Not sure if this should be logged in Teiid Designer or Teiid
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2617) "Teiid Connection>>Source Model" fails for HBase Datasource
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2617?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2617:
----------------------------------------
[~mmakovy] Any chance you have a HBase instance you could test this with on linux *and* windows to verify it's a windows configuration issue?
> "Teiid Connection>>Source Model" fails for HBase Datasource
> -----------------------------------------------------------
>
> Key: TEIIDDES-2617
> URL: https://issues.jboss.org/browse/TEIIDDES-2617
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.2
> Reporter: Debbie Steigner
>
> "Teiid Connection>>Source Model" fails for HBase Datasource. The JDBC importer works. Error in the server log:
> When trying to import into the Designer with Teiid Connection, it errors on the Importvdb metadata load with "ERROR 1101 (XCL01): ResultSet is closed.":
> 14:46:33,771 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "importVDB-vdb.xml" (runtime-name: "importVDB-vdb.xml")
> 14:46:33,825 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB importVDB.1 model "importVDBSrcModel" metadata is currently being loaded. Start Time: 8/4/15 2:46 PM
> 14:46:33,825 INFO [org.teiid.CONNECTOR] (teiid-async-threads - 1) HBaseExecutionFactory Commit=true;DatabaseProductName=Phoenix;DatabaseProductVersion=4.3;DriverMajorVersion=4;DriverMajorVersion=3;DriverName=PhoenixEmbeddedDriver;DriverVersion=4.3;IsolationLevel=2
> 14:46:33,951 INFO [org.jboss.as.server] (management-handler-thread - 8) JBAS015859: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml")
> 14:46:34,210 WARN [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: ERROR 1101 (XCL01): ResultSet is closed.
> 14:46:35,736 INFO [org.teiid.RUNTIME] (MSC service thread 1-7) TEIID50026 VDB "importVDB.1[importVDBSrcModel{importVDBSrcModel=importVDBSrcModel, hbase, java:/PhoenixDS}]" undeployed.
> Saw this https://developer.jboss.org/thread/260099, customer is getting the same winutils error and they state: This error usually comes when the hadoop server is accessed from windows machine.
> we get this error in other windows environment but this does not affect the application.
> Not sure if this should be logged in Teiid Designer or Teiid
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2732) Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2732?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2732:
-----------------------------------
Fix Version/s: 9.0.5
> Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-2732
> URL: https://issues.jboss.org/browse/TEIIDDES-2732
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export, Patch Release
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 9.0.5, 9.2.1
>
> Attachments: TestcaseforImport.zip
>
>
> AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS POINTS TO WRONG COLUMNS IN SOURCE MODEL
> Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> XML INPUT fragment for Source model, table CatalogItem:
> CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID),
> CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID)
> Expected in Teiid:
> CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> Actual:
> CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(ID)
> 3. AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS IS MISSING IN VIEW MODEL.
> Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> XML INPUT fragment for View model, table CatalogItem:
> CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID),
> CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID)
> Expected in Teiid:
> CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> Actual:
> Not Foreign key reference at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2731) VDB exported to Dynamic VDB XML, the foreign key relations have erroneous references in the resulting SQL.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2731?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2731:
-----------------------------------
Fix Version/s: 9.0.5
> VDB exported to Dynamic VDB XML, the foreign key relations have erroneous references in the resulting SQL.
> -------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2731
> URL: https://issues.jboss.org/browse/TEIIDDES-2731
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export, Patch Release
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 9.0.5, 9.2.1
>
> Attachments: TestcaseforExport.zip
>
>
> Model:
> • Catalog (ID, SecondID, ThirdID). Primary key: (ID). Unique constraint: (SecondID, ThirdID)
> • CatalogItem(ID,CatalogID, CatalogSecondID, CatalogThirdID)
> Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> Expected in metadata DLL for CatalogItem:
> CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID)
> Actual:
> CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(ID)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months