*: Add tidb flags document #1
Merged
Conversation
This file contains 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
| @@ -0,0 +1,50 @@ | |||
| # Configuration flags | |||
|
|
|||
| TiDB is configurable through command-line flags and environment variables. | |||
|
@queenypingcap PTAL |
|
|
||
| ### --lease | ||
| + Schema lease time in second. | ||
| + The schema lease time in second. |
|
@queenypingcap PTAL |
| ### --perfschema | ||
| + Enable(1) or disable(0) the performance schema. | ||
| + default: "0" | ||
| + The value can be (1) or (0). (1) is to enable and (0) is to disable. If the value is set to be (1), the performance will be affected. |
There was a problem hiding this comment.
Should explain when or why we need to set it to 1.
|
PTAL @coocood @queenypingcap |
| + default: "0" | ||
| + The value can be (1) or (0). (1) is to enable and (0) is to disable. If the value is set to be (1), the performance will be affected. | ||
| + The value can be (1) or (0). (1) is to enable and (0) is to disable. The Performance Schema provides a way to inspect internal execution of the server at runtime. See [performance schema](http://dev.mysql.com/doc/refman/5.7/en/performance-schema.html) for more information. If enable performance schema, the performance will be affected. |
There was a problem hiding this comment.
If you enable the performance schema, the performance will be affected.
|
@queenypingcap PTAL |
|
LGTM |
dveeden
referenced
this pull request
in dveeden/docs
Dec 3, 2021
http://company.funyours.co.jp/ redirects to https://www.funyours.co.jp and that host doesn't present a correct/complete certificate chain. In addition to that it looks like the certificate and hostname don't match. https://www.ssllabs.com/ssltest/analyze.html?d=www.funyours.co.jp Previous discussion: pingcap#6837 (comment) ``` $ curl -v -L http://company.funyours.co.jp/ * Trying 210.152.118.91:80... * Connected to company.funyours.co.jp (210.152.118.91) port 80 (#0) > GET / HTTP/1.1 > Host: company.funyours.co.jp > User-Agent: curl/7.79.1 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Fri, 03 Dec 2021 06:37:29 GMT < Content-Type: text/html < Content-Length: 178 < Connection: keep-alive < Location: https://www.funyours.co.jp < * Ignoring the response-body * Connection #0 to host company.funyours.co.jp left intact * Issue another request to this URL: 'https://www.funyours.co.jp/' * Trying 47.245.16.139:443... * Connected to www.funyours.co.jp (47.245.16.139) port 443 (#1) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt * CApath: none * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (OUT), TLS alert, unknown CA (560): * SSL certificate problem: unable to get local issuer certificate * Closing connection 1 curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. ```
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Dec 3, 2021
http://company.funyours.co.jp/ redirects to https://www.funyours.co.jp and that host doesn't present a correct/complete certificate chain. In addition to that it looks like the certificate and hostname don't match. https://www.ssllabs.com/ssltest/analyze.html?d=www.funyours.co.jp Previous discussion: pingcap#6837 (comment) ``` $ curl -v -L http://company.funyours.co.jp/ * Trying 210.152.118.91:80... * Connected to company.funyours.co.jp (210.152.118.91) port 80 (#0) > GET / HTTP/1.1 > Host: company.funyours.co.jp > User-Agent: curl/7.79.1 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Fri, 03 Dec 2021 06:37:29 GMT < Content-Type: text/html < Content-Length: 178 < Connection: keep-alive < Location: https://www.funyours.co.jp < * Ignoring the response-body * Connection #0 to host company.funyours.co.jp left intact * Issue another request to this URL: 'https://www.funyours.co.jp/' * Trying 47.245.16.139:443... * Connected to www.funyours.co.jp (47.245.16.139) port 443 (pingcap#1) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt * CApath: none * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (OUT), TLS alert, unknown CA (560): * SSL certificate problem: unable to get local issuer certificate * Closing connection 1 curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. ```
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Dec 3, 2021
http://company.funyours.co.jp/ redirects to https://www.funyours.co.jp and that host doesn't present a correct/complete certificate chain. In addition to that it looks like the certificate and hostname don't match. https://www.ssllabs.com/ssltest/analyze.html?d=www.funyours.co.jp Previous discussion: pingcap#6837 (comment) ``` $ curl -v -L http://company.funyours.co.jp/ * Trying 210.152.118.91:80... * Connected to company.funyours.co.jp (210.152.118.91) port 80 (#0) > GET / HTTP/1.1 > Host: company.funyours.co.jp > User-Agent: curl/7.79.1 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Fri, 03 Dec 2021 06:37:29 GMT < Content-Type: text/html < Content-Length: 178 < Connection: keep-alive < Location: https://www.funyours.co.jp < * Ignoring the response-body * Connection #0 to host company.funyours.co.jp left intact * Issue another request to this URL: 'https://www.funyours.co.jp/' * Trying 47.245.16.139:443... * Connected to www.funyours.co.jp (47.245.16.139) port 443 (pingcap#1) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt * CApath: none * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (OUT), TLS alert, unknown CA (560): * SSL certificate problem: unable to get local issuer certificate * Closing connection 1 curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. ```
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Dec 3, 2021
http://company.funyours.co.jp/ redirects to https://www.funyours.co.jp and that host doesn't present a correct/complete certificate chain. In addition to that it looks like the certificate and hostname don't match. https://www.ssllabs.com/ssltest/analyze.html?d=www.funyours.co.jp Previous discussion: pingcap#6837 (comment) ``` $ curl -v -L http://company.funyours.co.jp/ * Trying 210.152.118.91:80... * Connected to company.funyours.co.jp (210.152.118.91) port 80 (#0) > GET / HTTP/1.1 > Host: company.funyours.co.jp > User-Agent: curl/7.79.1 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Fri, 03 Dec 2021 06:37:29 GMT < Content-Type: text/html < Content-Length: 178 < Connection: keep-alive < Location: https://www.funyours.co.jp < * Ignoring the response-body * Connection #0 to host company.funyours.co.jp left intact * Issue another request to this URL: 'https://www.funyours.co.jp/' * Trying 47.245.16.139:443... * Connected to www.funyours.co.jp (47.245.16.139) port 443 (pingcap#1) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt * CApath: none * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (OUT), TLS alert, unknown CA (560): * SSL certificate problem: unable to get local issuer certificate * Closing connection 1 curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. ```
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Dec 3, 2021
http://company.funyours.co.jp/ redirects to https://www.funyours.co.jp and that host doesn't present a correct/complete certificate chain. In addition to that it looks like the certificate and hostname don't match. https://www.ssllabs.com/ssltest/analyze.html?d=www.funyours.co.jp Previous discussion: pingcap#6837 (comment) ``` $ curl -v -L http://company.funyours.co.jp/ * Trying 210.152.118.91:80... * Connected to company.funyours.co.jp (210.152.118.91) port 80 (#0) > GET / HTTP/1.1 > Host: company.funyours.co.jp > User-Agent: curl/7.79.1 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Fri, 03 Dec 2021 06:37:29 GMT < Content-Type: text/html < Content-Length: 178 < Connection: keep-alive < Location: https://www.funyours.co.jp < * Ignoring the response-body * Connection #0 to host company.funyours.co.jp left intact * Issue another request to this URL: 'https://www.funyours.co.jp/' * Trying 47.245.16.139:443... * Connected to www.funyours.co.jp (47.245.16.139) port 443 (pingcap#1) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt * CApath: none * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (OUT), TLS alert, unknown CA (560): * SSL certificate problem: unable to get local issuer certificate * Closing connection 1 curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. ```
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Dec 3, 2021
http://company.funyours.co.jp/ redirects to https://www.funyours.co.jp and that host doesn't present a correct/complete certificate chain. In addition to that it looks like the certificate and hostname don't match. https://www.ssllabs.com/ssltest/analyze.html?d=www.funyours.co.jp Previous discussion: pingcap#6837 (comment) ``` $ curl -v -L http://company.funyours.co.jp/ * Trying 210.152.118.91:80... * Connected to company.funyours.co.jp (210.152.118.91) port 80 (#0) > GET / HTTP/1.1 > Host: company.funyours.co.jp > User-Agent: curl/7.79.1 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Fri, 03 Dec 2021 06:37:29 GMT < Content-Type: text/html < Content-Length: 178 < Connection: keep-alive < Location: https://www.funyours.co.jp < * Ignoring the response-body * Connection #0 to host company.funyours.co.jp left intact * Issue another request to this URL: 'https://www.funyours.co.jp/' * Trying 47.245.16.139:443... * Connected to www.funyours.co.jp (47.245.16.139) port 443 (pingcap#1) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt * CApath: none * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (OUT), TLS alert, unknown CA (560): * SSL certificate problem: unable to get local issuer certificate * Closing connection 1 curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. ```
breezewish
pushed a commit
that referenced
this pull request
Jun 25, 2024
* feat: initialize the vector search document structure * fix: merge toc * fix * feat: add langchain + llamaindex integration guide * feat: add jinaai embedding integration guide * vector search: refine wording (#1) * vector search: refine wording * Discard changes to tidb-cloud/create-tidb-cluster-serverless.md * remove "cluster with vector search enabled" * Update tidb-cloud/vector-search-overview.md * Apply suggestions from code review Co-authored-by: Mini256 <minianter@foxmail.com> --------- Co-authored-by: Mini256 <minianter@foxmail.com> * feat: add peewee + sqlalchemy integration guide * feat: add django integration quickstart * add supported distance functions * fix: add faqs --------- Co-authored-by: Aolin <aolinz@outlook.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.