oceanbase / oceanbase/pyseekdb
[Bug]: Failed to check whether table exist or not?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 62
- Forks
- 35
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 2
Description
Describe the bug
When I use this code to check whether table exist or not?
# Check if table exists
if not client.has_collection(table_name):
logger.warning(
f"Table {table_name} does not exist, returning default component_mapping"
)
return component_mapping.copy()
it will report this table doesn't exist.
Environment
Fast reproduce steps
I have check source code of "client.has_collection(table_name)"
I will use "describe {table_name}" but I doesn't know why it failed.
Expected behavior
No response
Actual behavior
No response
Additional context
The whole source code locate at https://github.com/ob-labs/ChatBot
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with client.has_collection(table_name) and the describe {table_name} path identified in the report; reproduce the false “doesn't exist” result using the linked ChatBot source. Done means the false-negative case is explained and the existence check's behavior is verified against the intended table.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100