{
  "prog.predictor": {
    "lm": null,
    "traces": [],
    "train": [],
    "demos": [
      {
        "augmented": true,
        "query": "I am designing a table based on TiDB's TTL feature, but when I try to create the table using a cluster created with Serverless, I get a `'TTL' is not supported on TiDB Serverless` error.\n\nI plan to use Dedicated on my production environment and Serverless on my development environment, so it would be helpful if the TTL feature could be used in a Serverless environment.\n\nI've read the documentation that says Serverless will support TTL features in the future, but is there a specific timeline for this?\n\nAlso, is it possible to prevent TTL syntax from causing errors in Serverless?",
        "subquestions": "```json\n{\n  \"questions\": [\n    {\n      \"question\": \"Why is the TTL feature not supported on TiDB Serverless?\",\n      \"reasoning\": \"Understanding the current limitations of TiDB Serverless regarding the TTL feature.\"\n    },\n    {\n      \"question\": \"Is there a specific timeline for when TiDB Serverless will support the TTL feature?\",\n      \"reasoning\": \"The user wants to know when they can expect the TTL feature to be available in TiDB Serverless.\"\n    },\n    {\n      \"question\": \"How can I prevent TTL syntax from causing errors in TiDB Serverless?\",\n      \"reasoning\": \"The user needs a workaround to avoid errors when using TTL syntax in their development environment.\"\n    },\n    {\n      \"question\": \"What are the differences between TiDB Serverless and TiDB Dedicated regarding TTL feature support?\",\n      \"reasoning\": \"Understanding the differences will help the user plan their production and development environments effectively.\"\n    }\n  ]\n}\n```"
      },
      {
        "augmented": true,
        "query": "What are the feature changes in the latest version compared to v7.0 for TiDB?",
        "subquestions": "```json\n{\n  \"questions\": [\n    {\n      \"question\": \"What is the latest version of TiDB?\",\n      \"reasoning\": \"To compare feature changes, we need to identify the latest version of TiDB.\"\n    },\n    {\n      \"question\": \"What are the new features introduced in the latest version of TiDB?\",\n      \"reasoning\": \"To understand the changes, we need to know what new features have been added in the latest version.\"\n    },\n    {\n      \"question\": \"What features were present in TiDB v7.0?\",\n      \"reasoning\": \"To make a comparison, we need to know the features available in TiDB v7.0.\"\n    },\n    {\n      \"question\": \"What features have been removed or deprecated in the latest version compared to v7.0?\",\n      \"reasoning\": \"Identifying removed or deprecated features helps in understanding the differences between the two versions.\"\n    },\n    {\n      \"question\": \"What are the improvements or changes in existing features from v7.0 to the latest version?\",\n      \"reasoning\": \"To provide a comprehensive comparison, we need to know how existing features have been improved or changed.\"\n    }\n  ]\n}\n```"
      },
      {
        "augmented": true,
        "query": "summary the performance improvement from version 6.5 to newest version for TiDB",
        "subquestions": "```json\n{\n  \"questions\": [\n    {\n      \"question\": \"What is the newest version of TiDB?\",\n      \"reasoning\": \"To understand the performance improvements, we first need to identify the latest version of TiDB.\"\n    },\n    {\n      \"question\": \"What were the performance metrics and benchmarks for TiDB version 6.5?\",\n      \"reasoning\": \"To compare performance improvements, we need to establish a baseline by understanding the performance metrics of version 6.5.\"\n    },\n    {\n      \"question\": \"What are the performance metrics and benchmarks for the newest version of TiDB?\",\n      \"reasoning\": \"To identify improvements, we need to know the performance metrics of the latest version.\"\n    },\n    {\n      \"question\": \"What specific performance improvements have been made from TiDB version 6.5 to the newest version?\",\n      \"reasoning\": \"This question directly addresses the user's query by comparing the performance metrics between the two versions.\"\n    },\n    {\n      \"question\": \"Are there any notable features or optimizations in the newest version that contribute to performance improvements?\",\n      \"reasoning\": \"Understanding the features or optimizations that lead to performance improvements can provide deeper insights into the changes made.\"\n    }\n  ]\n}\n```"
      },
      {
        "query": "tidb lighting to sync to serverless cluster,but the load command and the tidb-lighting tools dont have the tls config like --ssl-ca or --ca. so i can not sync to the full back data to the serverless",
        "subquestions": "{\"questions\":[{\"question\":\"Sync data to a serverless cluster using TiDB Lighting.\",\"reasoning\":\"The user case what the user wants to achieve\"},{\"question\":\"How to configure TLS for TiDB Lightning?\",\"reasoning\":\"The basic question what the user itentionally asked.\"},{\"question\":\"The sync issue is caused by the lack of TLS configuration options for TiDB Lightning.\",\"reasoning\":\"The problem that the user is facing.\"}]}"
      },
      {
        "query": "We are new to TiDB and don't quite understand the potential impact on our application architecture. We are using TiDB for audit logs and continue to direct traffic to TiDB. We noticed a sudden jump ID from 1 to 30,001. Are there any impacts? Do we need to address this? If we have 100 connections from several applications, what will happen? In summary, what should we do for Auto Increment or do nothing?",
        "subquestions": "{\"questions\":[{\"question\":\"Why Auto Increment in TiDB causes a sudden increase in the ID values?\",\"reasoning\":\"The main concerns that the user itentionally asked.\"},{\"question\":\"How 100 connections from several applications affect TiDB, especially when the Auto Increment causes a sudden jump in ID values?\",\"reasoning\":\"The second most important question that the user itentionally asked.\"},{\"question\":\"TiDB is used for storing audit logs and receiving continuous traffic.\",\"reasoning\":\"The user case what the user wants to achieve\"}]}"
      },
      {
        "query": "Upgrade TiDB Serverless to 7.4 or latest for enhanced MySQL 8.0 compatibility",
        "subquestions": "{\"questions\":[{\"question\":\"TiDB 7.4 or the latest version enhances compatibility with MySQL 8.0\",\"reasoning\":\"The reasoning why user wants to upgrade TiDB Serverless to 7.4 or latest for enhanced MySQL 8.0 compatibility\"},{\"question\":\"How to upgrade TiDB Serverless?\",\"reasoning\":\"The basic question what the user itentionally asked.\"}]}"
      },
      {
        "query": "I am current using tidb serverless, but as my product grows, I really need a dalicated cluster. Is there a solution helps finish the migration?",
        "subquestions": "{\"questions\":[{\"question\":\"How to migrate from TiDB serverless to TiDB dedicated cluster?\",\"reasoning\":\"The main concern of the user.\"}]}"
      },
      {
        "query": "Chat2query is returning an error message saying \"Query timeout expired\". Additionally, I am unable to locate this SQL query in the slow query log.",
        "subquestions": "{\"questions\":[{\"question\":\"Chat2query is returning an error message saying 'Query timeout expired'.\",\"reasoning\":\"The main problem the user is facing.\"},{\"question\":\"The reason why not to locate the SQL query in the slow query log.\",\"reasoning\":\"The secondary problem the user is facing.\"}]}"
      }
    ],
    "signature_instructions": "You are an expert in knowledge base graph construction, specializing in building comprehensive knowledge graphs.\nYour current task is to deconstruct the user's query into a series of step-by-step questions.\n\n## Instructions:\n\n1. Dependency Analysis:\n\n    - Analyze the user's query to identify the underlying dependencies and relationships between different components.\n    - Construct a dependency graph that visually represents these relationships.\n\n2. Question Breakdown: Divide the query into a sequence of step-by-step questions necessary to address the main query comprehensively.\n\n3. Provide Reasoning: Explain the rationale behind each question.\n\n4. Constraints:\n    - Limit the output to no more than 5 questions to maintain focus and relevance.\n    - Ensure accuracy by reflecting the user's true intentions based on the provided query.\n    - Ground all questions in factual information derived directly from the user's input.",
    "signature_prefix": "Subquestions:"
  }
}