base on A multi-modal vector database that supports upserts and vector queries using unified SQL (MySQL-Compatible) on structured and unstructured data, while meeting the requirements of high concurrency and ultra-low latency. # DingoDB [DingoDB](https://github.com/dingodb/dingo) is an open-source distributed multimodal vector database designed and developed by [DataCanvas](https://www.datacanvas.com/). It integrates multiple features such as online strong consistency, relational semantics, and vector semantics, making it a unique multimodal database product. In addition, DingoDB has excellent horizontal scalability and scaling capabilities, easily meeting enterprise-level high availability requirements. At the same time, it supports multiple language interfaces and is fully compatible with the MySQL protocol, providing users with high flexibility and convenience. DingoDB demonstrates comprehensive and outstanding advantages in terms of functionality, performance, and ease of use, bringing users an unprecedented data management experience.  ## Key Features **1. Comprehensive access interface** DingoDB provides comprehensive access interfaces, supporting various flexible access modes such as SQL, SDK, and API to meet the needs of different developers. Additionally, it introduces Table and Vector as first-class citizen data models, providing users with efficient and powerful data processing capabilities. **2.Built-in data high availability** DingoDB provides fully functional and highly available built-in configurations without the need to deploy any external components, which can significantly reduce users' deployment and operation and maintenance costs and significantly improve the efficiency of system operation and maintenance. **3.Fully automatic elastic data sharding** DingoDB supports dynamic configuration of data shard size, automatic splitting and merging, realizing efficient and friendly resource allocation strategies, and easily responding to various business expansion needs. **4.Scalar-vector hybrid retrieval** DingoDB supports both traditional database index types and various vector index types, providing a seamless scalar and vector hybrid retrieval experience, reflecting industry-leading retrieval capabilities. In addition, it also supports fusion of scalars and vectors. Distributed transaction processing. **5.Built-in real-time index optimization** DingoDB can build scalar and vector indexes in real time, providing users with unconscious background automatic index optimization. At the same time, it ensures no delays during data retrieval. ## Related Projects about DingoDB Welcome to visit [DingoDB](https://github.com/dingodb/dingo). The documentation of DingoDB is located on the website: [https://dingodb.readthedocs.io](https://dingodb.readthedocs.io). The main projects about DingoDB are as follows: - [DingoDB](https://github.com/dingodb/dingo): A Unified SQL Engine to parse and compute for both structured and unstructured data. - [Dingo-Store](https://github.com/dingodb/dingo-store): A strongly consistent distributed storage system based on the Raft protocol. - [Dingo-Deploy](https://github.com/dingodb/dingo-deploy): The deployment project of compute nodes and storage nodes. ## Get Start ### Docs All Documentation [Docs](https://dingodb.readthedocs.io/en/latest/) ### Install How to install and deploy [Docker](https://dingodb.readthedocs.io/en/latest/deployment/deploy_in_single_node_using_docker.html) or [Ansible](https://dingodb.readthedocs.io/en/latest/deployment/deploy_on_cluster_by_ansible.html#) ### Usage How to use DingoDB [Usage](https://dingodb.readthedocs.io/en/latest/usage/how_to_use_dingodb.html) ## Developing DingoDB We recommend IntelliJ IDEA to develop the DingoDB codebase. Minimal requirements for an IDE are: * Support for Java * Support for Gradle ### How to make a clean pull request - Create a personal fork of dingo on GitHub. - Clone the fork on your local machine. Your remote repo on GitHub is called origin. - Add the original repository as a remote called upstream. - If you created your fork a while ago be sure to pull upstream changes into your local repository. - Create a new branch to work on. Branch from develop. - Implement/fix your feature, comment your code. - Follow the code style of Google code style, including indentation. - If the project has tests run them! - Add unit tests that test your new code. - In general, avoid changing existing tests, as they also make sure the existing public API is unchanged. - Add or change the documentation as needed. - Squash your commits into a single commit with git's interactive rebase. - Push your branch to your fork on GitHub, the remote origin. - From your fork open a pull request in the correct branch. Target the Dingo's develop branch. - Once the pull request is approved and merged you can pull the changes from upstream to your local repo and delete your branch. - Last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code. ### IntelliJ IDEA The IntelliJ IDE supports Java and Gradle out of the box. Download it at [IntelliJ IDEA website](https://www.jetbrains.com/idea/). ## Special Thanks ### DataCanvas DingoDB is Sponsored by [DataCanvas](https://www.datacanvas.com/), a new platform to do data science and data process in real-time. ### Java Profiler tools: YourKit [](https://www.yourkit.com/java/profiler/index.jsp) I highly recommend YourKit Java Profiler for any preformance critical application you make. Check it out at https://www.yourkit.com/ DingoDB is an open-source project licensed in **Apache License Version 2.0**, welcome any feedback from the community. For any support or suggestion, please contact us. ## Contact us If you have any technical questions or business needs, please contact us. Attach the Wetchat QR Code  Attach the Offical Account QR Code  ", Assign "at most 3 tags" to the expected json: {"id":"10152","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"