[pull] trunk from spiceai:trunk#808
Merged
Merged
Conversation
Add a Docker Hub login step (using DOCKERHUB_USERNAME / DOCKERHUB_TOKEN) to every workflow that pulls images from Docker Hub, so all pulls use the authenticated rate limits instead of anonymous (per-IP) limits. Covers: - Direct `docker pull` of postgres / mysql in the four bench workflows. - `docker run registry:2` (Docker Hub) in spiced_docker.yml, spiced_docker_dev.yml, and build_nightly.yml. - `docker/build-push-action` jobs whose Dockerfiles `FROM` Docker Hub bases (debian, rust, ubuntu, nvidia/cuda) in spiced_docker.yml (amd64/arm64/cuda), spiced_docker_dev.yml, build_nightly.yml, spidapter_build_and_release.yml, and testoperator_build_and_release.yml. Each new step is gated on `github.repository == 'spiceai/spiceai'` so it is a no-op on forks (which don't have access to the secrets).
Co-authored-by: Spice Schema Bot <schema-bot@spice.ai> Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>
…10700) * docs: refresh README with v2.0 capabilities and recent improvements Update README.md to reflect the substantial work shipped since the last refresh: cluster-sidecar architecture, Apache Ballista distributed query, Cayenne/Vortex acceleration, Iceberg writes, S3 Vectors, Postgres native WAL CDC, multi-vector embeddings, rerank UDTF, Spice Skills for AI coding agents, and new connectors/secret stores. Reorganizes the page to lead with concrete benchmarks and link out to the recent engineering deep-dive blog posts and YouTube talks (CMU, AWS re:Invent 2025). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: keep original sample output timestamps in README Revert log-output timestamps in the Quickstart example back to the original 2025-01-20 sample so the snippet remains a faithful capture. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: relax latency claim from sub-millisecond to millisecond Replace "sub-millisecond" with "millisecond" in the README hero line and "Why Spice?" bullet to keep the localhost-latency claim honest. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: surface Text-to-SQL/NSQL in the README "What you get" list Promote the existing NSQL capability to a top-level API in the runtime overview so readers see text-to-SQL alongside SQL, OpenAI, Iceberg, and MCP. NSQL was previously only mentioned in the use-case section. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: lead differentiators with the cluster-sidecar architecture Rework the "How is Spice different?" list to put the cluster-sidecar architecture first, with structural data sandboxing and ingest-once / serve-everywhere as the supporting differentiators. Three-tier latency, credential isolation, and identical spicepod.yaml across OSS / Cloud / Enterprise are now called out explicitly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: fix broken Apache Ballista link in README ballista.apache.org no longer resolves; Ballista is hosted under the DataFusion subproject at datafusion.apache.org/ballista/. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: point Slack links to spice.ai/slack Update README Slack badge and Connect-with-us link from spiceai.org/slack to spice.ai/slack so they resolve to the current shared-invite URL. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: remove Discord from README community links Drop the Discord invite from the Connect-with-us list — community conversation now happens on Slack, X, and LinkedIn. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: address Copilot reviewer comments on README - Standardize blog URLs on spice.ai/blog (header nav and Connect-with-us) - Use text fences for Claude Code slash commands; split shell vs slash - Fix Iceberg and Bedrock table-row trailing-space alignment - Replace ― with ❌ in comparison tables to match the legend - Drop unexplained asterisk on the Embeddings table LLM Format(s) header - Spell out RC as Release Candidate in the Secret Stores table - Capitalize FROM in the Dockerfile snippet - Clarify cluster mode: --role scheduler for schedulers, --scheduler-address for executors joining them, with runtime.scheduler.state_location config Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: address second-pass Copilot review on README - Vector engines table: drop pgvector / sqlite_vec / duckdb_vector (not accepted by .vectors.engine) and rename duckdb_vector → duckdb to match the runtime; only s3_vectors, duckdb, and elasticsearch are supported as vector engines today - Update hybrid-search bullet and section to match the actual engines - Fix aws_secrets → aws_secrets_manager (the runtime's registered name per crates/runtime-secrets/src/lib.rs:97) - Make the closing CTA release-agnostic so it doesn't reference v2.0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: address third-pass Copilot review on README - Reword "five industry-standard APIs" to "five APIs and interfaces" since Text-to-SQL (NSQL) is a capability rather than a standardized protocol. - Embeddings table: describe `openai` as an embeddings endpoint (not LLM endpoint) and realign column spacing. --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )