[JBoss JIRA] (TEIIDDES-2748) ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2748?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2748:
-----------------------------------
Fix Version/s: 12.0
(was: 11.2.1)
> ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
> ---------------------------------------------------------------------------------------------…
[View More]--------------------------------------------------------------------------
>
> Key: TEIIDDES-2748
> URL: https://issues.jboss.org/browse/TEIIDDES-2748
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.3, 9.2
> Reporter: Debbie Steigner
> Assignee: Ted Jones
> Priority: Minor
> Fix For: 12.0
>
>
> Using the ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
> On the Source and WSDL Operations Definitions screen, the selected WSDL does validate. All the WSDL Operatoins are visible and selected.
> On the Models Definition screen the folders are setup and the names are unique. The recommended User-specified Procedures is checked.
> On the Procedure definition screen for EVERY operation has the warning “No columns are defined for the response result set for the operation:<name of operation>
> The Schema Contents section is blank. I can easily trace the very obvious connections through the wsdl to the associated schema that defines the complex type and the individual elements that compose it for every method. The add button doesn’t work.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3217) Error reading Foreign Keys from Mysql 8.0
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3217?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-3217:
------------------------------------------
[~cjohn001] 1046 looks to be the mysql error code from that exception. You should be able to see a full stack trace in the server log. If that's the case, it's like that the connection string for the mysql connections do not include the target database.
> Error reading Foreign Keys from Mysql 8.0
> ------------------…
[View More]-----------------------
>
> Key: TEIIDDES-3217
> URL: https://issues.jboss.org/browse/TEIIDDES-3217
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 11.1.3
> Reporter: Christoph John
> Priority: Major
>
> I am currently trying to use TEIID designer together with a mysql 8.0 database to import a source model. Unfortunately, foreign keys cannot be read correctly. I assume it has to do with the VISIBLE flag on the index. Is there a known workaround available for mysql 8.0?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3217) Error reading Foreign Keys from Mysql 8.0
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3217?page=com.atlassian.jira.plu... ]
Christoph John edited comment on TEIIDDES-3217 at 11/2/18 3:04 PM:
-------------------------------------------------------------------
Hallo Steven,
I played now for a while with the different Teiid importer settings in hope to get the model running with teiid. However, still without success. I am not sure if it is a single issue or several with the database.
As a matter of principe I have two schemes in the …
[View More]database and during testing made several observations.
- Partly, tables have the same name in the different schemas. Seems this results in conflicts during import. I played around with the catalog option. This resulted in the correct tables selected. But for one table still a foreign key was missing.
- I than removed one database. The exported source model looked ok at the beginning. However, the deployed model is not running at all. If I try to access the tables I just get errors. For example:
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID30504</code>
<message>
TEIID30504 my_nutri_diary: 1046 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.`fkProfile` AS c_0, g_0.`AvatarImg` AS c_1 FROM `Avatar` AS g_0 WHERE g_0.`fkProfile` = 1 ORDER BY c_0]
</message>
</error>
when reading a table entry. As I have not found an option to attach a file in the following I will attach my complete db. I hope that you can reproduce the issue with the full model. If you are interested I could also provide a docker image with the database. However, I would need a place for upload.
Best regards,
Christoph
-- MySQL Workbench Forward Engineering
SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL,ALLOW_INVALID_DATES';
-- -----------------------------------------------------
-- Schema service_center
-- -----------------------------------------------------
-- -----------------------------------------------------
-- Schema service_center
-- -----------------------------------------------------
CREATE SCHEMA IF NOT EXISTS `service_center` DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ;
-- -----------------------------------------------------
-- Schema my_nutri_diary
-- -----------------------------------------------------
-- -----------------------------------------------------
-- Schema my_nutri_diary
-- -----------------------------------------------------
CREATE SCHEMA IF NOT EXISTS `my_nutri_diary` DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ;
USE `service_center` ;
-- -----------------------------------------------------
-- Table `service_center`.`Profile`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `service_center`.`Profile` (
`idProfile` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
`uuidUser` CHAR(36) CHARACTER SET 'ascii' BINARY NOT NULL,
PRIMARY KEY (`idProfile`),
UNIQUE INDEX `uuidUser_UNIQUE` (`uuidUser` ASC) VISIBLE)
ENGINE = InnoDB
COMMENT = 'Table stores a mapping between user profiles and uuids of keycloak accounts';
-- -----------------------------------------------------
-- Table `service_center`.`Avatar`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `service_center`.`Avatar` (
`fkProfile` BIGINT UNSIGNED NOT NULL,
`AvatarImg` BLOB NULL,
UNIQUE INDEX `fkProfile_UNIQUE` (`fkProfile` ASC) VISIBLE,
PRIMARY KEY (`fkProfile`),
CONSTRAINT `fkProfileInAvatar`
FOREIGN KEY (`fkProfile`)
REFERENCES `service_center`.`Profile` (`idProfile`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
USE `my_nutri_diary` ;
-- -----------------------------------------------------
-- Table `my_nutri_diary`.`Profile`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `my_nutri_diary`.`Profile` (
`idProfile` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
`uuidUser` CHAR(36) CHARACTER SET 'ascii' BINARY NOT NULL,
PRIMARY KEY (`idProfile`),
UNIQUE INDEX `uuidUser_UNIQUE` (`uuidUser` ASC) VISIBLE)
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `my_nutri_diary`.`Avatar`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `my_nutri_diary`.`Avatar` (
`fkProfile` BIGINT UNSIGNED NOT NULL,
`AvatarImg` BLOB NULL,
UNIQUE INDEX `fkProfile_UNIQUE` (`fkProfile` ASC) VISIBLE,
PRIMARY KEY (`fkProfile`),
CONSTRAINT `fkProfileInAvatar`
FOREIGN KEY (`fkProfile`)
REFERENCES `my_nutri_diary`.`Profile` (`idProfile`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `my_nutri_diary`.`BiometricProfile`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `my_nutri_diary`.`BiometricProfile` (
`fkProfile` BIGINT UNSIGNED NOT NULL,
`Age` INT UNSIGNED NULL,
`BodyHeight` INT UNSIGNED NULL,
`Gender` ENUM('m', 'w') NULL,
`BirthDate` DATE NULL,
INDEX `fkProfileInBiometricProfile_idx` (`fkProfile` ASC) VISIBLE,
UNIQUE INDEX `fkProfile_UNIQUE` (`fkProfile` ASC) VISIBLE,
PRIMARY KEY (`fkProfile`),
CONSTRAINT `fkProfileInBiometricProfile`
FOREIGN KEY (`fkProfile`)
REFERENCES `my_nutri_diary`.`Profile` (`idProfile`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `my_nutri_diary`.`BodyWeight`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `my_nutri_diary`.`BodyWeight` (
`idBodyWeight` BIGINT UNSIGNED NOT NULL COMMENT 'We need a surrogate key here as Teiid requires a primary key on each table. fkProfile is not unique here as we can will have multiple weight measurements per person. Moreover, combining it with WeightMeasurementDateTime makes the index to compute intensive.',
`fkProfile` BIGINT UNSIGNED NOT NULL,
`WeightMeasurementDateTime` DATETIME NOT NULL,
`Weight` TINYINT UNSIGNED NOT NULL,
INDEX `fkProfileInBodyWeight_idx` (`fkProfile` ASC) VISIBLE,
PRIMARY KEY (`idBodyWeight`),
CONSTRAINT `fkProfileInBodyWeight`
FOREIGN KEY (`fkProfile`)
REFERENCES `my_nutri_diary`.`Profile` (`idProfile`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;
was (Author: cjohn001):
Hallo Steven,
I played now for a while with the different Teiid importer settings in hope to get the model running with teiid. However, still without success. I am not sure if it is a single issue or several with the database.
> Error reading Foreign Keys from Mysql 8.0
> -----------------------------------------
>
> Key: TEIIDDES-3217
> URL: https://issues.jboss.org/browse/TEIIDDES-3217
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 11.1.3
> Reporter: Christoph John
> Priority: Major
>
> I am currently trying to use TEIID designer together with a mysql 8.0 database to import a source model. Unfortunately, foreign keys cannot be read correctly. I assume it has to do with the VISIBLE flag on the index. Is there a known workaround available for mysql 8.0?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 5 months
[JBoss JIRA] (TEIIDDES-3217) Error reading Foreign Keys from Mysql 8.0
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3217?page=com.atlassian.jira.plu... ]
Christoph John commented on TEIIDDES-3217:
------------------------------------------
Hallo Steven,
I played now for a while with the different Teiid importer settings in hope to get the model running with teiid. However, still without success. I am not sure if it is a single issue or several with the database.
> Error reading Foreign Keys from Mysql 8.0
> -----------------------------------------
>
&…
[View More]gt; Key: TEIIDDES-3217
> URL: https://issues.jboss.org/browse/TEIIDDES-3217
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 11.1.3
> Reporter: Christoph John
> Priority: Major
>
> I am currently trying to use TEIID designer together with a mysql 8.0 database to import a source model. Unfortunately, foreign keys cannot be read correctly. I assume it has to do with the VISIBLE flag on the index. Is there a known workaround available for mysql 8.0?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 5 months
[JBoss JIRA] (TEIIDDES-2964) Add capability to set a default data role grant
by Andrea Modesto Rossi (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2964?page=com.atlassian.jira.plu... ]
Andrea Modesto Rossi edited comment on TEIIDDES-2964 at 11/2/18 5:18 AM:
-------------------------------------------------------------------------
Perfect!
(Restricted to jira-users group)
was (Author: amrossi):
Perfect!
> Add capability to set a default data role grant
> -----------------------------------------------
>
> Key: TEIIDDES-2964
> URL: https://issues.…
[View More]jboss.org/browse/TEIIDDES-2964
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: VDB & Execution
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.2.1
>
> Attachments: Clear All Permissions.png, Default Role Access.png, Remove All Permissions Confirmation.png
>
>
> We use JDV as "data-firewall", so there are a lot of groups configured on JDV data roles section.
> Each time we add a model object to the project, by default all read permission are granted to that model for all groups.
> We think it could be better, to have an option in the "Data Roles" tab, avoiding users to uncheck for all the groups's permission which aren't needed (see page 2 attachment JDV_RFE_security_default_profile).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 5 months
[JBoss JIRA] (TEIIDDES-2964) Add capability to set a default data role grant
by Andrea Modesto Rossi (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2964?page=com.atlassian.jira.plu... ]
Andrea Modesto Rossi commented on TEIIDDES-2964:
------------------------------------------------
Perfect!
> Add capability to set a default data role grant
> -----------------------------------------------
>
> Key: TEIIDDES-2964
> URL: https://issues.jboss.org/browse/TEIIDDES-2964
> Project: Teiid Designer
> Issue Type: Feature Request
…
[View More]> Components: VDB & Execution
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.2.1
>
> Attachments: Clear All Permissions.png, Default Role Access.png, Remove All Permissions Confirmation.png
>
>
> We use JDV as "data-firewall", so there are a lot of groups configured on JDV data roles section.
> Each time we add a model object to the project, by default all read permission are granted to that model for all groups.
> We think it could be better, to have an option in the "Data Roles" tab, avoiding users to uncheck for all the groups's permission which aren't needed (see page 2 attachment JDV_RFE_security_default_profile).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 5 months
[JBoss JIRA] (TEIIDDES-2964) Add capability to set a default data role grant
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2964?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2964 at 11/1/18 11:39 AM:
------------------------------------------------------------------
[~dsteigne][~amrossi]I attached 3 screen caps showing a solution. Could you check it out and comment?
* For new Data Roles, I added a confirmation dialog titled *Default Role Access* asking the user "Do you wish to create role with no default read, write, update, delete …
[View More]permissions?". If YES, then no default READ permissions are applied
* Once in the Data Role Wizard, users have a *Clear All Permissions* which, if pressed, will display a confirmation dialog titled *Remove All Permissions* which warns user this will clear all current permissions for the data role.
* Note that new data roles have Grant All = FALSE by default
* Executing *Clear All Permissions* will also sets Grant All to FALSE
was (Author: blafond):
[~dsteigne][~amrossi]I attached 3 screen caps showing a solution. Could you check it out and comment?
* For new Data Roles, I added a confirmation dialog titled *Default Role Access* asking the user "Do you wish to create role with no default read, write, update, delete permissions?". If YES, then no default READ permissions are applied
* Once in the Data Role Wizard, users have a *Clear All Permissions* which, if pressed, will display a confirmation dialog titled *Remove All Permissions* which warns user this will clear all current permissions for the data role.
> Add capability to set a default data role grant
> -----------------------------------------------
>
> Key: TEIIDDES-2964
> URL: https://issues.jboss.org/browse/TEIIDDES-2964
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: VDB & Execution
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.2.1
>
> Attachments: Clear All Permissions.png, Default Role Access.png, Remove All Permissions Confirmation.png
>
>
> We use JDV as "data-firewall", so there are a lot of groups configured on JDV data roles section.
> Each time we add a model object to the project, by default all read permission are granted to that model for all groups.
> We think it could be better, to have an option in the "Data Roles" tab, avoiding users to uncheck for all the groups's permission which aren't needed (see page 2 attachment JDV_RFE_security_default_profile).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 5 months
[JBoss JIRA] (TEIIDDES-2964) Add capability to set a default data role grant
by Debbie Steigner (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2964?page=com.atlassian.jira.plu... ]
Debbie Steigner commented on TEIIDDES-2964:
-------------------------------------------
[~blafond] Looks good to me, wait to see what the customer, [~amrossi] thinks.
> Add capability to set a default data role grant
> -----------------------------------------------
>
> Key: TEIIDDES-2964
> URL: https://issues.jboss.org/browse/TEIIDDES-2964
> …
[View More]Project: Teiid Designer
> Issue Type: Feature Request
> Components: VDB & Execution
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.2.1
>
> Attachments: Clear All Permissions.png, Default Role Access.png, Remove All Permissions Confirmation.png
>
>
> We use JDV as "data-firewall", so there are a lot of groups configured on JDV data roles section.
> Each time we add a model object to the project, by default all read permission are granted to that model for all groups.
> We think it could be better, to have an option in the "Data Roles" tab, avoiding users to uncheck for all the groups's permission which aren't needed (see page 2 attachment JDV_RFE_security_default_profile).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 5 months