[MCOL-1250] Can't select different path for Columnstore.xml file through the PDI Created: 2018-03-07  Updated: 2023-10-26  Resolved: 2018-03-09

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: None
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Elena Kotsinova (Inactive) Assignee: Elena Kotsinova (Inactive)
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

CentOS 7, PDI 8

Attachments: JPEG File PDI_Bulk_Load_Settings.JPG    

 Description   

PDI Spoon design tool provides possibility to select ColumStore.xml file location. See attached screenshot.
But selection is not taken in consideration and loader continues to search this file in exact location: /usr/local/mariadb/columstore/etc

Expected:
Take the file from the pointed location in settings of the Bulk Loader different from default one.



 Comments   
Comment by Jens Röwekamp (Inactive) [ 2018-03-08 ]

Can't reproduce the error in CentOS7 and PDI8.

When I hit browse in the module and select a different Columnstore.xml configuration, its path appears in the highlighted input box and the different Columnstore instance is connected.

Tested with following configuration:

Local CentOS 7 running PDI and CS1.1.2, and remote Debian 9 running CS1.1.2.

Created local table test.t1 (i int, c char), and remote table test.t2 (i int, c char) through mcsmysql.

/usr/local/mariadb/columnstore/etc/Columnstore.xml points to the local CS instance.
/usr/local/mariadb/columnstore/etc/Columnstore-remote.xml points to the remote (Debian 9) CS instance.

Connected a "Data Grid" block (i int, c String) with data to the "MariaDB ColumnStore Bulk Loader" block and opened its configuration.
Changed target database to "test" and target table to "t1", then hit "map all inputs".

As the default configuration was selected, the compatible rows state yes. Then changed target table to "t2" and confirmed that the compatible rows state no.

Afterwards changed the configuration to "/usr/local/mariadb/columnstore/etc/Columnstore-remote.xml" (by using the browse button) and verified that the compatible rows state yes. Then changed target table to t1 and confirmed that the compatible rows state no.

---------

Could you provide me with more information so that I can reproduce your error? Helpful would for example be your setup used and the Columnstore.xml file selected.

Comment by Elena Kotsinova (Inactive) [ 2018-03-09 ]

Confirmed selection of the xml file from different location works in PDI 7.1. and PDI 8 for CentOS 7. It seems that I forgot to save the transformation module during my initial tests.

Generated at Thu Feb 08 02:27:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.