I installed an extension on magento store. Name of the extension is Mirasvit Advanced Product Feeds The extension was in a zip file. After installing the extension, I started a validation test for the installed extension from the admin panel and i got this error:
Table 'feedexport/feed' not exists Table 'feedexport/feed_history' not
exists Table 'feedexport/template' not exists Table
'feedexport/custom_attribute' not exists Table
'feedexport/performance_click' not exists Table
'feedexport/performance_order' not exists Table
'feedexport/performance_aggregated' not exists Table 'feedexport/rule'
not exists Table 'feedexport/rule_product' not exists Table
'feedexport/rule_feed' not exists Table 'feedexport/feed_product' not
exists Table 'feedexport/mapping_category' not exists
I also check core_resource table and no Mirasvit extension related data found.
Related
I have renamed one column name cust_addr to customer_address from Customers table, using below query:
Alter table Customers rename column cust_addr to customer_address;
Now, when am trying to access the data from Customers table, am getting below error:
Select * from Customers;
[Code: 6482, SQL State: VX001] [Vertica][VJDBC](6482) ERROR: Failed to parse Access Policies for table "Customers" [Column "cust_addr" does not exist]
I have checked this cust_addr column is not present in Customers tables now. But still getting this error.
Can anyone please help me to resolve this.
Find the access policy that is not working now:
SELECT * FROM access_policy WHERE table_name='Customers' AND column_name='cust_addr';
Keep that information.
Then -
DROP ACCESS POLICY ON Customer FOR COLUMN cust_addr;
.. And create the new access policy for customer_address.
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'm2loom_live.customer_entity_back' doesn't exist, query was: SELECT DISTINCT child.custome r_id FROM authorlogin_customer AS child
LEFT JOIN customer_entity_back AS parent ON child.customer_id = parent.entity_id WHERE (child.customer_id IS NOT NULL) AND (parent.entity_id IS NUL
L)
enter image description here
Looking at that table name (m2loom_live) I'm guessing that table comes from an extension or a customization you may have put in. Those tables need to exist before you can migrate their rows to your new database. To do that you will need to either install the Magento 2 version of that extension or recreate your module and add an install script (or better yet a db_schema.xml) file, and then run bin/magento setup:upgrade to create the table. Then you should be able to migrate the data to your new database.
If you don't want to keep that table then you will have to modify or extend the data-migration-tool's mapping files to tell it to ignore that table instead of trying to migrate its data. I'm not 100% on this part, but I think the mapping file you would want to edit would be map.xml and you would add:
<document_rules><!-- This is the element you need to add your configuration too -->
...
<ignore>
<document>Your Table Here</document>
</ignore>
Assuming we have 2 hive tables created under the same HDFS file path.
I want to be able to drop a table WITH the HDFS files path, without corrupting the other table that's in the same shared path.
By doing the following:
drop table test;
Then:
hadoop fs -rm -r hdfs/file/path/folder/*
I delete both tables files, not just the one I've dropped.
In another post I found this solution:
--changing the tbl properties to to make the table as internal
ALTER TABLE <table-name> SET TBLPROPERTIES('EXTERNAL'='False');
--now the table is internal if you drop the table data will be dropped automatically
drop table <table-name>;
But I couldn't get passed the ALTER statement as I got a permission denied error (User does not have [ALTER] privilege on table)
Any other solution?
If you have two tables using the same location, then all files in this location belongs to both tables, does not matter how they were created.
Say if you have table1 with location hdfs/file/path/folder and table2 with the same location hdfs/file/path/folder and you inserted some data into table1, files are created and they are being read if you select from table2, and vice-versa: if you insert into table2, new files will be accessible from table1. This is because table data is being stored in the location, no matter how you put the files inside that location. You can insert data into table using SQL, put files into location manually, etc.
Each table or partition has it's location, you cannot specify files separately.
For better understanding, read also this answer with examples about multiple tables on top of the same location: https://stackoverflow.com/a/54038932/2700344
Does anyone know how to connect voyager to an existing table?
If the table doesn't exits one would go to Database=>Create and specify a name and columns and create a table which would display at the tables list but what do we do when there is a table?
I tried just filling the form and clicked the "Create new table" button and received "table already exists" error which was obvious.
If the table is already present in the same database as of your laravel project. Then it should be displayed in your list of tables under the Voyager->Databases
For ex : In the below snapshot, there was a table 'testtbl' which was already created by me. So it is getting reflected in the "Voyager => Databases"
I have trouble when I click on Admin -> CMS -> Page and I get 404error. Maybe any body had this error early? How to debug router in magento? and i think this is community or local extensions.
I explain the error she code
in app/code/core/Mage/Adminhtml/Block/Cms/Page/Grid.php
$collection->setFirstStoreFlag(true);
when, application get first store for get all pages on the first.
after if first storage in table cms_page_store not exist in table core_store then I get error and 404 error not found.
How to fix I run two queries on my mysql server first delete all not exist store in table core_page_store by this query
delete from `cms_page_store` where `store_id` not in(
select `core_store`.`store_id` as `id` from `core_store`
);
and delete all page in not exist store from cms_page by this query:
delete from `cms_page` where `page_id` not in(
select `cms_page_store`.`page_id` as `id` from `cms_page_store`
);
and finish it's work, please if you read the answer you need create dump table cms_page_store and cms_page for repair the table if you make error.