Redis Store Migration from 2.0.0-M10 to 2.0.0-M11

[sbernard31]

Changes :

Between 2.0.0-M10 and 2.0.0-M11, there is lot of changes in Redis Store I tried to list it just below 👇 :

Store	old key/prefix	new key/prefix	Data compatibility break	PR
RedisSecurityStore	SEC#EP#	SECSTORE#SEC#EP#	compatible	#1398
	PSKID#SEC	SECSTORE#EP#PSKID	compatible	#1398
RedisRegistrationStore	REG:EP:	REGSTORE#REG#EP#	not compatible	#1414 #1318
	EP:REGID:	REGSTORE#EP#REGID#	compatible	#1414
	EP:ADDR:	REGSTORE#EP#ADDR#	compatible	#1414
	EP:IDENTITY:	REGSTORE#EP#IDENTITY#	compatible	#1414
	LOCK:EP:	REGSTORE#LOCK#EP#	compatible	#1414
	OBS:TKN:	REGSTORE#OBS#TKN#	not compatible	#1414 #1318
	TKNS:REGID:	REGSTORE#TKNS#REGID#	compatible	#1414
	EXP:EP	REGSTORE#EXP#EP	compatible	#1414

Recommended Migration Way :

For RedisSecurityStore :

1. use old keys : new RedisSecurityStore.Builder(jedis).setPrefix(null).setEndpointByPskIdKey("PSKID#SEC").build();
2. OR write a migration script which renames keys (let us know if you write something like this)

For RedisRegistrationStore, as registration is just kind of "session", probably better to just drop all data and so force client to re-register.
Note that key name changed, so if you do nothing, registration will not be found and so client will re-register but old data will not be deleted.
Looking at #1401 (comment) could help.

Will it change again soon ?

We will not change this just for fun, but at the same time there are already some identified point which could lead to new changes:

• Transport Layer abstraction is very young, so could changes again.
• How to handle data format Compatibility break in Redis Store ? #1417
• Should Registration be strictly tied to a server endpoint ? #1415
• Redesign peer's Identity class.  #1436

ℹ️ So, IF you don't specially need M11 new feature AND you are using Redis Store AND you can not migrate easily THEN maybe better to wait for a next releases. ℹ️

[sbernard31]

From 2.0.0-M11 to 2.0.0-M12

We break again RedisRegistrationStore data format with #1436.
For Key REGSTORE#REG#EP#, Registration identity field was replaced by transportdata field which a completely different way to serialize.
For Key REGSTORE#EP#IDENTITY#, Identity has completely different way to be serialized.

For RedisRegistrationStore, as registration is just kind of "session", easy way to migrate could be to just drop all data and so force client to re-register.

[sbernard31]

From 2.0.0-M16 to 2.0.0-M17

We break again RedisRegistrationStore data format with #1656.

• REGSTORE#OBS#TKN# prefix is now named REGSTORE#OBS#OBSID#. The key using this prefix is no more followed by the observation Token (as byte array) but by observation identifier (as byte array like "endpointUri##token").
• REGSTORE#TKNS#REGID# prefix is now named REGSTORE#OBSIDS#REGID#. The value indexed by this key no more contains a list of token but a list of observation identifier (as byte array like "endpointUri##token").

For RedisRegistrationStore, as registration is just kind of "session", easy way to migrate could be to just drop all data and so force client to re-register.