[#2856] fix(core): Fix the namespace missing issue when get entities from kv storage

[jerryshao]

What changes were proposed in this pull request?

This PR fixes the namespace missing issue when entities are gotten from kv storage.

Why are the changes needed?

Fix: #2856

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Modified UTs.

[yuqi1129]

@jerryshao

I noticed that you only set the namespace value when deserialization and will not store the value in the key-value store. My question is: Why do we have to change the interface EntitySerDe instead of setting it(namespace value) in the caller method?

[yuqi1129]

This folder does not exist on my local machine, can anyone help to confirm this point?

[jerryshao]

Try gradle build.

[jerryshao]

@jerryshao

I noticed that you only set the namespace value when deserialization and will not store the value in the key-value store. My question is: Why do we have to change the interface EntitySerDe instead of setting it(namespace value) in the caller method?

You can check the issue to know the details. Simply, it is because the deserialized entity from KV has an empty namespace, but for catalog like kafka needs to get namespace from entity to use, and it cannot get a namespace from context (caller), you can see KafkaOperation's CatalogInfo (CatalogEntity).

Besides, for relational store, they all have namespace set when get from interface, so it is also a behavior alignment.

[yuqi1129]

@jerryshao

I noticed that you only set the namespace value when deserialization and will not store the value in the key-value store. My question is: Why do we have to change the interface EntitySerDe instead of setting it(namespace value) in the caller method?

You can check the issue to know the details. Simply, it is because the deserialized entity from KV has an empty namespace, but for catalog like kafka needs to get namespace from entity to use, and it cannot get a namespace from context (caller), you can see KafkaOperation's CatalogInfo (CatalogEntity).

Besides, for relational store, they all have namespace set when get from interface, so it is also a behavior alignment.

I see, let me check again

[yuqi1129]

It's okay with me.

[mchades]

LGTM