-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate entry "reques path" although different store_id #26
Comments
I am just now encountering a similar problem. The problem on your Magento 1 database seems to be that it returns more than one row for the following SQL query: As you can see with the command Maybe you can delete the duplicate entry? I do not know if it is wise, though. |
If you want to know how many duplicates you have, run this: SELECT request_path, store_id, COUNT(*) as count
FROM <your magento 1 database>.core_url_rewrite
GROUP BY request_path, store_id
HAVING COUNT(*) > 1; |
I don't know what the problem could be, unfortunately. May I ask how you solved your first problem? |
I have removed duplicate records and the issue has been solved. |
Alright, then I think I will do the same, at least for the test migration. Thank you. |
Do you have any idea with my second issue? |
#16 mentions a similar problem, I think. Maybe it helps? If not, you may want to begin to debug, probably the |
@bh-ref I have the same issue. However, your query given above returns nothing on m1 DB (changed to enterprise_url_rewrite) The data migration tool will fail on upright-vacuum-cleaners/swift-upright which exists for store 22 and store 4 etc. However they are unique as it appends the store id??
|
@craigcarnell I never encountered the case where a duplicate was automatically resolved like it seems to be the case in your log. However, I had another problem with URL Rewrite step. It turned out, that the affected rewrite had like some fields missing (NULL) whereas other rewrite did not have NULLs in the same fields (columns). Maybe you can look up your affected rewrites in your DB and check with other rewrites which where successful to detect a difference/error? |
I am trying migration tool 2.0.2 and I have this issue:
In my magento 1 db in enterprise_url_rewrite: SELECT * FROM enterprise_url_rewrite WHERE request_path LIKE '%upright-vacuum-cleaners/swift-upright%' AND store_id=22; |
Also:
When there is only 2 in different stores:
|
It looks like in 32cba04 the duplicate resolution what changed to only modify paths with a "." in them. Not sure why this change was added, but it seems to completely break duplicate resolution for many paths. |
Additionally duplicates are queried and pulled by priority, but when the resolution occurs the record that is inserted into the database that does NOT have its request_path modified doesn't get the target_path or redirect_type for the highest priority duplicate. |
Any updates on this Magento??? |
@yaronish @victor-v-rad can you help? |
I suggest #81 is the same. I have created internal issue to process this case |
@ilol Any updates on this issue? This is the last issue preventing me from handing over a decent M1 database -> M2 |
I'm also experiencing this issue. 1.9.0.1 to 2.0.7 migration. Only 1 instance of the combination that is throwing the error: |
@ilol I still get this issue with 2.1 |
will fix this in the next sprint (MAGETWO-52505) |
@craigcarnell, we currently work on this issue. Could you please provide us with your |
@ygrigoriev do you have an e-mail address or some how to send you this data? |
@craigcarnell |
I don't now why I can't migrate url_rewrite table with same "request path" value but different store_id.
I think this is a bug of this tool.
Do you have any idea?
The text was updated successfully, but these errors were encountered: