[IGNITE-21900] meta --remove does not delete the <typeId>.classname0 file from db/marshaller causing errors on subsequent type re-registration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.16
• Fix Version/s: 2.17
• Component/s: general
• Assignee: Evgeny Stanilovsky
• Reporter: Evgeny Stanilovsky
• Created: 02/Apr/24 04:55
• Updated: 03/Apr/24 13:03
• Resolved: 03/Apr/24 13:03

Description

meta --remove command deletes the type from db/<binary-meta>/<node-id> but not from db/marshaller -
This causes errors if the server tries to re-create the type w/the same name but different case.

say the user created the type model.Account (upper case A)
CREATE TABLE my_table(..) WITH key_type=model.Accountkey,value_type=model.Account
then dropped the table, DROP TABLE my_table.
and ran a --meta remove --typeName mode.Account

If the users change the case of the type say from model.Account to model.account – one letter to lowercase
and then does a subsequent:
CREATE TABLE my_table(..) WITH key_type=model.accountkey,value_type=model.account

then does an INSERT, the server will come back with “Failed to register class”

Caused by: org.apache.ignite.internal.DuplicateTypeIdException: Duplicate ID [platformId=0, typeId=1853064544, oldCls=com.ual.cfa.fa.model.CFAFaPairNonFltDutyHistKey, newCls=com.ual.cfa.fa.model.CFAFaPairNonfltDutyHistKey]
	at org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:223) ~[ignite-core.jar]
	at org.apache.ignite.internal.binary.BinaryContext.registerUserClassName(BinaryContext.java:1185) ~[ignite-core-.jar]

Issue Links

• links to: GitHub Pull Request #11295