[MCOL-17] When tables failed to created in the ColumnStore backend, it is still created in the MariaDB Server front end Created: 2016-05-03 Updated: 2016-06-15 Resolved: 2016-05-31 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ExeMgr |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Dipti Joshi (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Need to make sure the two are in sync. |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2016-05-23 ] |
|
This seems to be storage engine integration issue. If the storage engine fails to create table - it needs to inform front end MariaDB Server - So it will not create the schema . dleeyh Please provide log of how this happened. |
| Comment by Dipti Joshi (Inactive) [ 2016-05-31 ] |
|
dleeyhThis was created as reported by your initial Autopilot run in February. Please reproduce it with latest binary. If you cannot please close it. |
| Comment by Daniel Lee (Inactive) [ 2016-05-31 ] |
|
Build tested: getsoftwareinfo Tue May 31 10:30:28 2016 Name : mariadb-columnstore-platform Relocations: (not relocatable) The latest Autopilot run did not show this issue. However, I believe the issue as described still exists since there fix was implemented. Autopilot just did hit the backend create table failure. We have three options here: 1) Spend time to induce an error condition to cause a table creation failure |
| Comment by Dipti Joshi (Inactive) [ 2016-05-31 ] |
|
dleeyh Let us close this now. We will open another item if the issue shows up agains. |
| Comment by Dipti Joshi (Inactive) [ 2016-05-31 ] |
|
As this is not occurring in latest build closing it. |