[MCOL-610] 1.08 backport MCOL-480 warning error reported after upgrade to 1.0.6 Created: 2017-03-07  Updated: 2017-03-23  Resolved: 2017-03-23

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

Type: Task Priority: Major
Reporter: David Thompson (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MCOL-480 warning error reported after upgrade ... Closed
Sprint: 2017-5, 2017-6

 Comments   
Comment by Daniel Lee (Inactive) [ 2017-03-22 ]

I reproduced the reported issue when upgrading from 1.0.4-1 to 1.0.6-1. After chatted with developer, we decided that it needs further investigation as the issue has observed since the fix.

My understand is that the messages were outputted incorrectly. The developer should provide a brief explanation on the situation so that others, myself included, would not think we are just suppressing the messages and the root cause of the issue was not fixed.

Comment by Daniel Lee (Inactive) [ 2017-03-22 ]

Build tested: 1.0.8-1
mcsadmin> getsoftware
getsoftwareinfo Wed Mar 22 21:53:39 2017
Name : mariadb-columnstore-platform
Version : 1.0.8
Release : 1
Architecture: x86_64
Install Date: Wed 22 Mar 2017 09:37:39 PM UTC
Group : Applications/Databases
Size : 10012539
License : Copyright (c) 2016 MariaDB Corporation Ab., all rights reserved; redistributable under the terms of the GPL, see the file COPYING for details.
Signature : (none)
Source RPM : mariadb-columnstore-platform-1.0.8-1.src.rpm
Build Date : Wed 22 Mar 2017 08:41:24 PM UTC

Have not seen the reported messages in a new installation.

The bug description talks about an upgrade. I don't know if it is an issue with the upgrade process. I will retest when the ticket is ready for QA again.

Comment by Daniel Lee (Inactive) [ 2017-03-23 ]

New installation of 1.0.6-1 also had the same issue. The issue was not related to the upgrade process. Closed per my test result in the last messages.

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