GitHub user Yicong-Huang edited a comment on the discussion: Refactor: Decoupling Direct Database Connection From ComputingUnitMaster & ComputingUnitWorker
The frontend environment is owned by a user, and we don't want 1) expose our backend details, I would push back on those information. a. resolved file path, which could show the actual file location in our backend (local or lakefs). b. worker machine location, I don't see it in the plan you posted, just want to make sure. 2) other user's information during compilation of shared sessions. I know logical plan possibly already have/expose them on the frontend, but we need to be careful on the compilation endpoint's access, and not to expose those to a wrong user. c. api keys (from Twitter operator, LLM operators, etc). d. DB source passwords, table, etc. GitHub link: https://github.com/apache/texera/discussions/5295#discussioncomment-17211362 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
