thoughtspot / thoughtspot/cs_tools
Errors after updating CS Tools version
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
First Stop
- I have read and agreed to the ThoughtSpot LICENSE.
- I understand that if I have a critical issue with ThoughtSpot, I should reach out to my designated Account Executive and Customer Success Manager instead of
cs_tools.
Platform Configuration
Description
After updating CS_Tools, cs_tools tools searchable metadata no longer runs without errors.
Considering adding a log file.
DatabaseError: (databricks.sql.exc.ServerOperationError) [INSUFFICIENT_PERMISSIONS] Insufficient privileges:
User does not have permission SELECT on any file. SQLSTATE: 42501
[SQL:
COPY INTO ts_cluster_e39b3
FROM 'dbfs:/FileStore/cs_tools/TMP_STAGE_ts_cluster_26018.csv'
FILEFORMAT = CSV
FORMAT_OPTIONS (
'header' = 'true',
'inferSchema' = 'true',
'delimiter' = '|'
)
COPY_OPTIONS ('mergeSchema' = 'true')
]
(Background on this error at: https://sqlalche.me/e/20/4xp6)
+--------------------- ?? This is an unhandled error! ?? ---------------------+
¦ ¦
¦ If you encounter this message more than once, please help by letting us know! ¦
¦ ¦
¦ GitHub: https://github.com/thoughtspot/cs_tools/issues/new/choose ¦
¦ ¦
+------------ Run cs_tools logs report to send us your last error. -------------+
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 the cs_tools tools searchable metadata command and reproduce the Databricks permission error shown for the COPY INTO operation. Use cs_tools logs report to capture context, then trace how the temporary CSV is loaded and verify that the command completes without the unhandled INSUFFICIENT_PERMISSIONS error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100