[#5536] Improvement(client-python): reportUndefinedVariable warning in types.py

[orenccl]

What changes were proposed in this pull request?

Update the type variables in the types.py

Why are the changes needed?

Fix: #5536

Does this PR introduce any user-facing change?

No

How was this patch tested?

Unit Test

[jerryshao]

Is it possible to add a lint check for such kind of Python warning in pyintrc?

[orenccl]

@jerryshao
I think currently pylint can not detect forward reference
https://peps.python.org/pep-0484/#forward-references

It can detect _instance: BooleanType = None
But can't detect _instance: "BooleanType" = None

[jerryshao]

I see, thanks.

[jerryshao]

Can you please check all the python codes to see if there's similar issue in other files, I think we can fix it all in this PR.

[orenccl]

Sure, I will update.

[orenccl]

Hi @xunliu
There are 3 Unresolved reference in client-python.gravitino.catalog.catalog.py

• Unresolved reference 'TableCatalog'
• Unresolved reference 'FilesetCatalog'
• Unresolved reference 'TopicCatalog'

I found FilesetCatalog has usage and it's class is located in gravitino.catalog.fileset_catalog.py

However, I couldn't resolve the other two (TableCatalog and TopicCatalog). Are these using forward references on purpose?

// Has usage and class type
def as_fileset_catalog(self) -> "FilesetCatalog":

// No usage and class type
def as_table_catalog(self) -> "TableCatalog":
def as_topic_catalog(self) -> "TopicCatalog":

Could you help me resolve these warning?