[MCOL-2102] postConfigure -port option leaves columnstore.xml CrossEngineSupport port unchanged Created: 2019-01-23  Updated: 2020-04-01  Resolved: 2019-10-11

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 1.0.0, 1.2
Fix Version/s: 1.4.1

Type: Bug Priority: Minor
Reporter: Thomas Boyd (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2019-06

 Description   

The MariaDB platform single container image uses the -port option of postConfigure to move the columnstore install off of 3306 to 4306. The columnstore.xml that is produced does have the main port info correclty on 4306, but we still get:

        <CrossEngineSupport>
 
                <Host>127.0.0.1</Host>
 
                <Port>3306</Port>
 
                <User>root</User>
 
                <Password/>
 
                <TLSCA/>
 
                <TLSClientCert/>
 
                <TLSClientKey/>
 
        </CrossEngineSupport>

I am pretty sure this should get changed too? This is particularly important because the AVRO router uses this field. Easy enough workaround (manual edit of columnstore.xml), but should get fixed at some point.

 Comments   
Comment by Roman [ 2019-06-25 ]

For QA: One should reinstall CS with setting port explicitly to 4406 and check whether CrossEngineSupport.Port is set to 4406.

Comment by Daniel Lee (Inactive) [ 2019-09-03 ]

My opinion is that this is an invalid bug. I verified 1.2.4-1 is working as designed.

postconfigure's -port command line parameter is to specify the port ColumnStore uses. For cross engine setup, the port parameter in the <CrossEngineSupport> section is to specify the port the remote SQL server used. By default, this is set to 3306. The user can change it if needed.

With the change implemented, rerunning postConfigure with the -port option will now also change the cross engine setting, which is not what we want. On the flip and positive side, the change will keep both ports the same by default if -port is used, which is useful when the remote server is the local server.

Keep or reject the new change?

Comment by Daniel Lee (Inactive) [ 2019-09-03 ]

The feature change should be reversed per my last command.

Thanks.

Comment by Andrew Hutchings (Inactive) [ 2019-10-02 ]

PR opened to revert commit

Comment by Andrew Hutchings (Inactive) [ 2019-10-07 ]

Back to QA due to test feature reverted.

Note: This should be closed as "Won't Fix" when passed QA

Comment by Daniel Lee (Inactive) [ 2019-10-11 ]

Build verified: 1.4.1-1

[dlee@master centos7]$ cat gitversionInfo.txt
engine commit:
5a4c406

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