shardingsphere
Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases
What XERJ indexed
Snapshot
The whole repository at commit 1791fc190a (2026-10-28). master is 24 commits ahead.
Selected work
“Fix select * is not supported for associated query”. 20 files, 1,148 lines in jdbc, proxy, test.
Licence
The repository
LICENSE file checked at the pinned commit; the author agreed to inclusion.
The XERJ corpus
The author agreed by email on 2026-10-31. Same terms as the repository. Answers name the repo, the commit and the file:line.
selected for the XERJ Corpus Hublicence clearedsuggested use: adapt with attribution
databasedistributed-databasedistributed-sql-databasesqlsharddatabase-clustermysqlpostgresql
Example questions
- How does shardingsphere implement database?
- Where does shardingsphere handle “Fix select * is not supported for associated query”?
- What does jdbc do in shardingsphere?
Inside the indexed corpus
- 17,859 files, 180.5 MB in total, about 10.4 KB per file.
- The selected commit changed 20 of those files (0.1%).
- Languages by size: Java 94.4%, ANTLR 3.6%, Python 1.5%, FreeMarker 0.3%, Shell 0.1%.
- On GitHub since 2016-01-18, last push 2026-10-31, 50,103 commits on master.
- The pin is 24 commits behind master; the corpus answers from the pinned code, not the newest.
Licence on GitHub and in the corpus
GitHub reported Apache-2.0 for apache/shardingsphere on 2026-10-31, and the LICENSE file at commit 1791fc190a was reviewed as Apache-2.0. They match, so answers from this corpus carry the same terms as the live repository.
Contributors
Claire (@ClaireLytt) has 1 selected repository on the hub.
Using XERJ with shardingsphere
- Search a SQL dump without restoring it shardingsphere is tagged database on GitHub.
- Index a monorepo so your agent stops reading the whole repo The pinned tree has 17,859 files.
- Ask questions about a GitHub repo without cloning it
- Index a reference library for a coding agent
The prompt
Paste it into your AI agent. It clones apache/shardingsphere at the pinned commit and indexes it on your machine.
Search the GitHub repository apache/shardingsphere with XERJ (https://hub.xerj.org/corpus/apache--shardingsphere). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/apache/shardingsphere shardingsphere && git -C shardingsphere checkout 1791fc190a8e4c6b90a7ecf0a27f92a197a5a8a0 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./shardingsphere --url http://127.0.0.1:9200 --prefix shardingsphere --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: Apache-2.0. Keep the copyright notice and credit the authors.
Related
ClaireDatabases and storage engines corporacloudnative-pgetcd-srcchdblibredb/libredb-studiotommyknocker/pdo-database-classpingcap/tidb
Stats: GitHub API, fetched 2026-10-31. Snapshot: the git tree at the pinned commit. Selected work and consent: the XERJ registry.