[ 
https://issues.apache.org/jira/browse/CARBONDATA-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Bhat updated CARBONDATA-3825:
------------------------------------
    Description: 
In 1.6.1 or 2.0 version create a table in a db in spark file format and insert 
records in the table.

Take a backup of the table store, drop database

In carbonsession using carbonextension create a database with same name as the 
db in sparkfileformat and copy table store of sparkfileformat to db path in 
hdfs.

Execute the refresh table command.

Refresh table fails with error "Table or view not found in database"

  was:
In 1.6.1 or 2.0 version create a table in a db in spark file format and insert 
records in the table.

Take a backup of the table store, drop database

In carbonsession using carbonextension create a database with same name as the 
db in sparkfileformat and copy table store of sparkfileformat .

Execute the refresh table command.

Refresh table fails with error "Table or view not found in database"


> Refresh table in carbonsession using carbonextension fails  for a table 
> created in sparkfile format
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-3825
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3825
>             Project: CarbonData
>          Issue Type: Bug
>          Components: data-load
>    Affects Versions: 2.0.0
>         Environment: Spark 2.3.2, 2.4.5
>            Reporter: Chetan Bhat
>            Priority: Major
>
> In 1.6.1 or 2.0 version create a table in a db in spark file format and 
> insert records in the table.
> Take a backup of the table store, drop database
> In carbonsession using carbonextension create a database with same name as 
> the db in sparkfileformat and copy table store of sparkfileformat to db path 
> in hdfs.
> Execute the refresh table command.
> Refresh table fails with error "Table or view not found in database"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to