streaming table created via sdk gets removed after 30 minutes
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- sql, typescript
Research direction
Start by reproducing a CREATE OR REFRESH STREAMING TABLE submission through the Node.js SDK and compare its behavior with the same command in the Databricks SQL editor. Investigate why the SDK-created table disappears after 30 minutes despite no DROP statement; done means identifying the cause and verifying that an SDK-created streaming table persists.
Written by the indexing model from the issue text.
Description
i am building an integration where i am submitting SQL to databricks via this SDK.
when i submit a CREATE OR REFRESH STREAMING TABLE command, it completes... but 30 minutes later, it just disappears from databricks completely.
when i create streaming tables via the sql editor in the databricks console, it seems to stick around, no problem.
i triple checked, and there are no DROP statements, or anything that we are doing to remove the streaming table.
here is some output from genie about this issue -
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 50
- Avg merge
- 13h 46m
- Merged PRs (30d)
- 9
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.
More from databricks/databricks-sql-nodejs
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
engineer-bot
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
databricks/databricks-sql-nodejs#274 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100