Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 【产品调研】你有需要 TiDB 支持 JSON 数据格式的应用场景吗?新款挎包抽奖送!
[Product Research for This Issue]
Do you have application scenarios that require TiDB to support JSON data format?
We look forward to everyone actively sharing current or needed application scenarios where TiDB supports JSON data format.
[What Problems Can JSON Solve]
For example: common format for network application storage, flexible data structures, access and analysis of semi-structured data, etc.
[Participate in the Research]
You can describe the usage scenario like this:
-
Application Scenario: (Industry) As a blockchain company, (Application Scenario) we need to collect various Web3 events, which have various flexible schema formats. Therefore, if we import all events into one table instead of creating thousands of small tables, JSON support can greatly improve development and management efficiency.
-
Demand Assessment: Strong demand, can greatly improve efficiency.
-
Technical Indicators: 10+ billion records, max size < 1kb; frequent queries and inserts, almost no updates needed.
-
Additional Notes: The most commonly used function is json_extract.
You can also provide feedback on the need for support for a specific JSON function below,
Reference: 请问tidb能支持mongodb那种对JSON中数组元素的索引吗 - TiDB 的问答社区
If you particularly, particularly, particularly need support for the JSON data format, you can also add me on WeChat: billmay, and I can arrange for you to have an in-depth chat with the PM about the future of JSON support.
[Research Participation Rewards]
50 experience points & points
[Lottery Rewards]
One lucky participant will receive a new shoulder bag.
[Follow-up Plan]
After the research, we will randomly select 3-5 participants with strong demand scenarios for 1v1 in-depth communication about product requirements. If there are iteration plans, they will be updated in this post as soon as possible.
Scenario: User comments or microtalk
Scenario: Similar to using Python web crawlers to fetch data, it can obtain user subscriptions and send advertisements based on their preferences.
Demand intensity: It’s just like my XML (Little Donkey), not much difference.
Yes, for example, when we connect with WeChat and Alipay, we often need to store JSON strings. Sometimes when doing rule parsing, especially dynamically, we generally use JSON.
Scenario: In the financial industry, using JSON for data such as holdings would be much more convenient.
Demand intensity: It’s for critical business use, and the demand is quite high.
Yes, obtain some raw data from third-party interfaces.
Yes, it is used for irregular data transformation processing, such as enterprise surveys.
Currently, it is supported as an experimental feature - JSON 类型 | PingCAP 文档中心
What I currently understand is that web crawlers, API returned data, and configuration files all require JSON data format. At present, I am practicing storing some data from a Python web crawler in MySQL in JSON format. There are definitely application scenarios for JSON data format, and the most I know about right now is web crawler data.
Supporting the JSON data format is a necessity. Currently, the required use cases include configuration information for various data sources and data returned by third-party interfaces, which need to use the JSON data format.
I think it’s not only necessary to support the JSON format, but also to support some JSON-related processing functions, so that using JSON can be more handy.
Please elaborate in detail~ For example, which functions~
There are scenarios that require it!
I have multiple different types of data that need to be unified into a single business data table. This table is used to describe the data of a company at various stages and trace its origins (such as company IPO application data, company IPO data, etc.).
Currently, to unify the data, I have a single data type in the table, and the data values are stored as JSON.