How to handle model names with '.' character

[xiaozcy]

I noticed that Gravitino does not support model names with '.' character, because this might demage the structure of 'catalog.shcema.model'. Are there any solutions to cover this?

In real scenarios, the name of the model may contain '.' character, such as 'Qwen2.5'. The unsupported character has caused compatibility difficulties for us to use Gravitino.

[jerryshao]

Currently we don't support “.” in the model name, because we use "." as a namespace delimiter, if there's a dot in the name, it will make the code confuse. Can you encode the "." when save the model name?

@mchades do you have other thoughts?

[xiaozcy]

Can you encode the "." when save the model name?

This might be a way, but it would reduce the readability of model names in Gravitino.

[mchades]

Currently we don't support “.” in the model name, because we use "." as a namespace delimiter, if there's a dot in the name, it will make the code confuse.

Agree. encoding . externally is one method.

Another approach is to allow users to use double quotes to represent each namespace level and name, ensuring they are not split during parsing. such as catalog.schema."Qwen2.5", catalog."schema.v1"."Qwen2.5"

[xiaozcy]

Another approach is to allow users to use double quotes to represent each namespace level and name, ensuring they are not split during parsing. such as catalog.schema."Qwen2.5", catalog."schema.v1"."Qwen2.5"

I think it's a better way, similar usage is supported in some sql engines, like SELECT * FROM catalog.schema.`table`.

[tedyu]

Another option without double quoting is to treat the 3rd dot (and beyond) as part of the model name.
e.g. for catalog.schema.Qwen2.5, Qwen2.5 is the model name.
This way, kafka topic names with dots are accommodated.

[mchades]

then how to handle the dot in the schema and catalog name?

[tedyu]

That requires bigger change. We can change the internal separator from dot to ^, e.g. catalog^schema.v1^Qwen2.5
The persisted model names prior to this change can be left as is - we treat the dots as ^.

Not sure if there has been such breaking change before.

[mchades]

What does "change the internal separator" mean here? Should the user be aware of this? How should it change for the user?

[tedyu]

internal separator first applies to in-memory representation where ^ is used.
It also applies to persisted form in data store.
The parsing logic is enhanced to search for ^ in the string. If ^ is not found, the format defaults to previous version.

bq. Should the user be aware of this?
There is no impact on user other than the allowance of using dots in model names.

The only tricky part is the downgrade path. If a system with new separator is downgraded, the target (lower) version must have patch which recognizes the new separator.

[mchades]

bq. Should the user be aware of this?
There is no impact on user other than the allowance of using dots in model names.

if the user want to List associated tags for a model (assume the model name includes dots), what should the curl be like?

[vladislav-kuryata]

Any updates here?
I guess we can use ‘ or ' delimiter like in MySQL or PG, I

[mchades]

Can you provide more detailed examples?