8000 Wishlist2 Table Not Replicated Due to Type System Name Suffix Conflict · Issue #41 · SAP/sap-commerce-db-sync · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Wishlist2 Table Not Replicated Due to Type System Name Suffix Conflict #41

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

Open
asad445 opened this issue Mar 13, 2025 · 0 comments
Open

Comments

@asad445
Copy link
asad445 commented Mar 13, 2025

We noticed that when the Hybris type system suffix is set to 2, the wishlist2 table is not replicated. This appears to be due to a conflict between the table name (wishlist2) and the type system name suffix (2).

Issue Details:
The wishlist2 table is missing from replication when the type system suffix is set.
To work around this, we removed the migration.ds.source.db.typesystemsuffix property, which allowed wishlist2 to be replicated successfully.

However, removing the suffix property causes other tables (e.g., enumerationvalues2, etc.) to not replicate as expected.

Expected Behavior:
All tables, including wishlist2 and suffix-based tables (e.g., enumerationvalues2), should replicate correctly regardless of the type system name suffix setting.

Steps to Reproduce:

Set migration.ds.source.db.typesystemsuffix=2 in the configuration.
Observe that wishlist2 is not replicated.
Remove the migration.ds.source.db.typesystemsuffix property.
Observe that wishlist2 is replicated, but other tables that rely on the suffix are not replicated then for example enumerationvalues2, composedtypes2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant
0