Messages by Thread
-
Monthly Texera Incubation Sync Meeting on June 30, Tuesday, 3:00 - 4:00 PM PDT
Xuan Gu
-
[D] Architecture discussion: how should the frontend and agent-service share backend API contracts? (REST contract drift) [texera]
via GitHub
-
[FYI] Texera v1.2.0-incubating RC2 planned for June 24
Xuan Gu
-
[D] Design and merge plan: operator output port result cache (MVP) [texera]
via GitHub
-
[D] Scala vs. Java: What's the future? [texera]
via GitHub
-
[D] Proposal: Add a user feedback option to Texera [texera]
via GitHub
-
[D] Improve resumable upload: track completion at the batch/session level [texera]
via GitHub
-
[D] Starter tasks for new contributors — 21 newly labeled (28 open in total) [texera]
via GitHub
-
[VOTE] Release Apache Texera (incubating) 1.2.0-incubating RC1
Xuan Gu
-
[D] Approach: unifying AWS (EKS) and on-premise Kubernetes deployment under bin/k8s — Helm-only vs eksctl vs Terraform [texera]
via GitHub
-
[D] Architecture discussion: multiple agent tool calls vs. a dedicated TexeraMCP server for exposing Texera functionality to the agent [texera]
via GitHub
-
[FYI] Texera v1.2.0-incubating release candidate planned for June 10
Xuan Gu
-
[D] Design: interactive grid for the operator result pane [texera]
via GitHub
-
[D] Proposal: Add Python Virtual Environments into the Left Panel and Workflow Canvas [texera]
via GitHub
-
[ANNOUNCE] Branch cut for v1.2 release line
Xuan Gu
-
[D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
Re: [D] Approach: landing Modern Observability (#4070) as a stack of small, self-contained PRs [texera]
via GitHub
-
[ANNOUNCEMENT] Xuan Gu will serve as the Release Manager for release line v1.2
Yicong Huang
-
[ANNOUNCE] Python Virtual Environment Support in Apache Texera
Sarah Asad
-
[CALL FOR VOLUNTEER] Release Manager for Apache Texera v1.2 release line
Yicong Huang
-
[RESULT][VOTE] Define the Release Manager role for Apache Texera releases
Yicong Huang
-
[DISCUSS] Treat Agents as another Resource on Texera
Jiadong Bai
-
[D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
Re: [D] Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units) [texera]
via GitHub
-
[DISCUSS] Decoupling the Computing Unit from direct database access
Jiadong Bai
-
[D] Refactor: Decoupling Database Connection From ComputingUnitMaster & ComputingUnitWorker [texera]
via GitHub
-
Seeking Feedback on Per-user Iceberg Warehouse Design
Meng Wang
-
[D] Per-user Iceberg warehouse with bring-your-own S3 storage [texera]
via GitHub
-
[VOTE] Define the Release Manager role for Apache Texera releases
Yicong Huang
-
[RESULT][VOTE] Adopt release branch naming and release cadence policy
Yicong Huang
-
[D] Discuss workflow macro design and lifecycle [texera]
via GitHub