This is an automated email from the ASF dual-hosted git repository.

yuqi4733 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/gravitino.git


The following commit(s) were added to refs/heads/main by this push:
     new 5144ed5df [#4666] docs: correct reference from MySQL to PostgreSQL in 
JDBC cata… (#4667)
5144ed5df is described below

commit 5144ed5dfd73ba1268b2e0aecd2076940f8ead90
Author: Saker <[email protected]>
AuthorDate: Sun Aug 25 21:23:01 2024 +0800

    [#4666] docs: correct reference from MySQL to PostgreSQL in JDBC cata… 
(#4667)
    
    <!--
    1. Title: [#4666] <type>(<scope>): <subject>
       Examples:
         - "[#123] feat(operator): support xxx"
         - "[#233] fix: check null before access result in xxx"
         - "[MINOR] refactor: fix typo in variable name"
         - "[MINOR] docs: fix typo in README"
         - "[#255] test: fix flaky test NameOfTheTest"
       Reference: https://www.conventionalcommits.org/en/v1.0.0/
    2. If the PR is unfinished, please mark this PR as draft.
    -->
    
    ### What changes were proposed in this pull request?
    
    The documents should be updated.
    
    ### Why are the changes needed?
    
    To correct reference from MySQL to PostgreSQL in JDBC catalog
    documentation.
    
    Fix: #4666
    
    ### Does this PR introduce _any_ user-facing change?
    
    No; Just the markdown documents.
    
    ### How was this patch tested?
    
    Manual review.
---
 docs/jdbc-postgresql-catalog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/jdbc-postgresql-catalog.md b/docs/jdbc-postgresql-catalog.md
index 3204b2436..6954ae673 100644
--- a/docs/jdbc-postgresql-catalog.md
+++ b/docs/jdbc-postgresql-catalog.md
@@ -31,7 +31,7 @@ Gravitino saves some system information in schema and table 
comment, like `(From
 
 ### Catalog properties
 
-Any property that isn't defined by Gravitino can pass to MySQL data source by 
adding `gravitino.bypass.` prefix as a catalog property. For example, catalog 
property `gravitino.bypass.maxWaitMillis` will pass `maxWaitMillis` to the data 
source property.
+Any property that isn't defined by Gravitino can pass to PostgreSQL data 
source by adding `gravitino.bypass.` prefix as a catalog property. For example, 
catalog property `gravitino.bypass.maxWaitMillis` will pass `maxWaitMillis` to 
the data source property.
 You can check the relevant data source configuration in [data source 
properties](https://commons.apache.org/proper/commons-dbcp/configuration.html)
 
 When you use the Gravitino with Trino. You can pass the Trino PostgreSQL 
connector configuration using prefix `trino.bypass.`. For example, using 
`trino.bypass.join-pushdown.strategy` to pass the `join-pushdown.strategy` to 
the Gravitino PostgreSQL catalog in Trino runtime.

Reply via email to