[
https://issues.apache.org/jira/browse/KYLIN-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guoliang Sun updated KYLIN-5991:
--------------------------------
Description:
# [Single-table Load/Refresh API] Incremental load without partition columns,
API does not throw an error.
# Failed to delete table without internal table
# [Single-table Refresh] Date out of range not validated
## When a time partition column exists and the selected date exceeds the range
of existing data, the refresh request does not throw an error and loads data
beyond the time range.
# [Kylin5 Upgrade] Kylin5 upgraded using the upgrade process, but the old
version directory was retained and not deleted.
# [Create Internal Table] Inconsistent transaction: Delta log was successfully
written, but the table metadata was not updated, causing subsequent creation of
this internal table to fail.
# When an internal table exists, the model cannot be hit by a query.
## Create a project and enable internal tables.
## Load the data source table.
## Create an internal table.
## Use this table for modeling and building.
## After the model is built, query the model. Expected to hit the model, but
the query shows pushdown (and pushdown does not hit the internal table).
# [Internal Table API] The URL parameters for table and database in the data
clearing interface are not separated.
## Need to be consistent with other internal table APIs, and pass the
parameters separately.
# [Source Table - Reload] After adding or deleting columns in the source
table, it is necessary to check whether the table is an internal table with
data during loading.
## If it is an internal table with data, reloading is not allowed. The user
should be prompted to clear the internal table data before reloading.
# [Internal Table API] The delete table partition interface does not validate
the 'partitions' parameter.
# [Internal Table API] The interface for getting internal table partition
details does not validate the database name and table name parameters.
## Passing non-existent values for the database name and table name results in
a successful response.
# [Internal Table API] When creating an internal table, the partition column
and time partition format are not cross-validated.
## The request succeeds when no partition column is passed, but only the time
partition format is provided.
# Normalizes the Error Code of the inner table apis
## The error message is unreasonable. When Accept-Language=cn is set, the
error message is still in English.
# Support Internal Table Open API
## Add a parameter to the table reload interface to support directly clearing
data and reloading the table (the UI will prompt users to clear the data
themselves before reloading).
was:
# [Single-table Load/Refresh API] Incremental load without partition columns,
API does not throw an error.
# Failed to delete table without internal table
# [Single-table Refresh] Date out of range not validated
## When a time partition column exists and the selected date exceeds the range
of existing data, the refresh request does not throw an error and loads data
beyond the time range.
# [KE5 Upgrade] KE5 upgraded using the upgrade process, but the old version
directory was retained and not deleted.
# [Create Internal Table] Inconsistent transaction: Delta log was successfully
written, but the table metadata was not updated, causing subsequent creation of
this internal table to fail.
# When an internal table exists, the model cannot be hit by a query.
## Create a project and enable internal tables.
## Load the data source table.
## Create an internal table.
## Use this table for modeling and building.
## After the model is built, query the model. Expected to hit the model, but
the query shows pushdown (and pushdown does not hit the internal table).
# [Internal Table API] The URL parameters for table and database in the data
clearing interface are not separated.
## Need to be consistent with other internal table APIs, and pass the
parameters separately.
# [Source Table - Reload] After adding or deleting columns in the source
table, it is necessary to check whether the table is an internal table with
data during loading.
## If it is an internal table with data, reloading is not allowed. The user
should be prompted to clear the internal table data before reloading.
# [Internal Table API] The delete table partition interface does not validate
the 'partitions' parameter.
# [Internal Table API] The interface for getting internal table partition
details does not validate the database name and table name parameters.
## Passing non-existent values for the database name and table name results in
a successful response.
# [Internal Table API] When creating an internal table, the partition column
and time partition format are not cross-validated.
## The request succeeds when no partition column is passed, but only the time
partition format is provided.
# Normalizes the Error Code of the inner table apis
## The error message is unreasonable. When Accept-Language=cn is set, the
error message is still in English.
# Support Internal Table Open API
## Add a parameter to the table reload interface to support directly clearing
data and reloading the table (the UI will prompt users to clear the data
themselves before reloading).
> Multiple abnormal errors in internal tables
> -------------------------------------------
>
> Key: KYLIN-5991
> URL: https://issues.apache.org/jira/browse/KYLIN-5991
> Project: Kylin
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Guoliang Sun
> Priority: Major
>
> # [Single-table Load/Refresh API] Incremental load without partition columns,
> API does not throw an error.
> # Failed to delete table without internal table
> # [Single-table Refresh] Date out of range not validated
> ## When a time partition column exists and the selected date exceeds the
> range of existing data, the refresh request does not throw an error and loads
> data beyond the time range.
> # [Kylin5 Upgrade] Kylin5 upgraded using the upgrade process, but the old
> version directory was retained and not deleted.
> # [Create Internal Table] Inconsistent transaction: Delta log was
> successfully written, but the table metadata was not updated, causing
> subsequent creation of this internal table to fail.
> # When an internal table exists, the model cannot be hit by a query.
> ## Create a project and enable internal tables.
> ## Load the data source table.
> ## Create an internal table.
> ## Use this table for modeling and building.
> ## After the model is built, query the model. Expected to hit the model, but
> the query shows pushdown (and pushdown does not hit the internal table).
> # [Internal Table API] The URL parameters for table and database in the data
> clearing interface are not separated.
> ## Need to be consistent with other internal table APIs, and pass the
> parameters separately.
> # [Source Table - Reload] After adding or deleting columns in the source
> table, it is necessary to check whether the table is an internal table with
> data during loading.
> ## If it is an internal table with data, reloading is not allowed. The user
> should be prompted to clear the internal table data before reloading.
> # [Internal Table API] The delete table partition interface does not
> validate the 'partitions' parameter.
> # [Internal Table API] The interface for getting internal table partition
> details does not validate the database name and table name parameters.
> ## Passing non-existent values for the database name and table name results
> in a successful response.
> # [Internal Table API] When creating an internal table, the partition column
> and time partition format are not cross-validated.
> ## The request succeeds when no partition column is passed, but only the
> time partition format is provided.
> # Normalizes the Error Code of the inner table apis
> ## The error message is unreasonable. When Accept-Language=cn is set, the
> error message is still in English.
> # Support Internal Table Open API
> ## Add a parameter to the table reload interface to support directly
> clearing data and reloading the table (the UI will prompt users to clear the
> data themselves before reloading).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
