commits  

Messages by Thread

• • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
  • Re: [PR] [AMORO-3775] Add support for metric-based refresh event trigger in TableRuntimeRefreshExecutor [amoro] via GitHub
• [I] [Subtask]: Add support for pluggable refresh event in TableRuntimeRefreshExecutor and DefaultRefreshEvent [amoro] via GitHub
  • Re: [I] [Subtask]: Add support for Metadata Metric-Driven refresh event [amoro] via GitHub
• [I] [Feature]: Event-Triggered Optimization of Iceberg Tables in Amoro [amoro] via GitHub
  • Re: [I] [Feature]: Event-Triggered Optimization of Iceberg Tables in Amoro [amoro] via GitHub
• Re: [I] [Bug]: Issue with Table Optimization Due to Duplicate Insertions [amoro] via GitHub
  • Re: [I] [Bug]: Issue with Table Optimization Due to Duplicate Insertions [amoro] via GitHub
  • Re: [I] [Bug]: Issue with Table Optimization Due to Duplicate Insertions [amoro] via GitHub
• Re: [I] [Bug]: The commit.retry.num-retries configuration does not take effect when configured on the catalog. [amoro] via GitHub
  • Re: [I] [Bug]: The commit.retry.num-retries configuration does not take effect when configured on the catalog. [amoro] via GitHub
  • Re: [I] [Bug]: The commit.retry.num-retries configuration does not take effect when configured on the catalog. [amoro] via GitHub
• Re: [I] [Improvement]: AK/SK Leakage Security [amoro] via GitHub
  • Re: [I] [Improvement]: AK/SK Leakage Security [amoro] via GitHub
  • Re: [I] [Improvement]: AK/SK Leakage Security [amoro] via GitHub
• Re: [I] [Bug]: Process deadlock causes the Amoro process to be stuck in committing permanently. [amoro] via GitHub
  • Re: [I] [Bug]: Process deadlock causes the Amoro process to be stuck in committing permanently. [amoro] via GitHub
  • Re: [I] [Bug]: Process deadlock causes the Amoro process to be stuck in committing permanently. [amoro] via GitHub
• Re: [I] [Bug]: Optimization records cannot be seen in some table details on Amoro UI [amoro] via GitHub
  • Re: [I] [Bug]: Optimization records cannot be seen in some table details on Amoro UI [amoro] via GitHub
  • Re: [I] [Bug]: Optimization records cannot be seen in some table details on Amoro UI [amoro] via GitHub
• Re: [I] [Improvement]: There are slow SQL issues when querying the optimizing process [amoro] via GitHub
  • Re: [I] [Improvement]: There are slow SQL issues when querying the optimizing process [amoro] via GitHub
  • Re: [I] [Improvement]: There are slow SQL issues when querying the optimizing process [amoro] via GitHub
• [PR] [AMORO-3772] Fix AuthenticatedHiveClientPool init fail and MixedTables#createChangeStore log printing error [amoro] via GitHub
  • Re: [PR] [AMORO-3772] Fix AuthenticatedHiveClientPool init fail and MixedTables#createChangeStore log printing error [amoro] via GitHub
  • Re: [PR] [AMORO-3772] Fix AuthenticatedHiveClientPool init fail and MixedTables#createChangeStore log printing error [amoro] via GitHub
• [PR] [AMORO-3698] Remove Flink 1.15 modules [amoro] via GitHub
  • Re: [PR] [AMORO-3698] Remove Flink 1.15 modules [amoro] via GitHub
  • Re: [PR] [AMORO-3698] Remove Flink 1.15 modules [amoro] via GitHub
• (amoro) branch master updated (41bc8cf28 -> b4cba4b11) jinsongzhou
  • (amoro) 05/05: fix MixedFormatSourceEnumStateSerializer serialize see flink 1.18 https://github.com/apache/flink/pull/21952/files jinsongzhou
  • (amoro) 02/05: fix flinksource test jinsongzhou
  • (amoro) 04/05: fix MixedFormatSourceEnumStateSerializer serialize see flink 1.18 https://github.com/apache/flink/pull/21952/files jinsongzhou
  • (amoro) 01/05: [AMORO-3697] add Flink 1.18 support for mixed-format jinsongzhou
  • (amoro) 03/05: fix checkstyle jinsongzhou
• [I] [Feature]: Improve the release procedure [amoro] via GitHub
  • Re: [I] [Feature]: Improve the release procedure [amoro] via GitHub
  • Re: [I] [Feature]: Improve the release procedure [amoro] via GitHub
• (amoro) branch master updated: [Improvement]: Introduce TableRuntimeFactory interface (#3760) baiyangtx
• [PR] [Amoro-3766][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3766][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3766][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3766][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
• [PR] [AMORO-3761] Fix licnese-binary [amoro] via GitHub
  • Re: [PR] [AMORO-3761] Fix licnese-binary [amoro] via GitHub
  • Re: [PR] [AMORO-3761] Fix licnese-binary [amoro] via GitHub
  • Re: [PR] [AMORO-3761] Fix licnese-binary [amoro] via GitHub
• [PR] [AMORO-3736]Add healthScoreDetails page to show details of healthScore [amoro] via GitHub
  • Re: [PR] [AMORO-3736]Add healthScoreDetails page to show details of healthScore [amoro] via GitHub
  • Re: [PR] [AMORO-3736]Add healthScoreDetails page to show details of healthScore [amoro] via GitHub
  • Re: [PR] [AMORO-3736]Add healthScoreDetails page to show details of healthScore [amoro] via GitHub
  • Re: [PR] [AMORO-3736]Add healthScoreDetails page to show details of healthScore [amoro] via GitHub
• (amoro) branch master updated: [AMORO-3761] Fix licnese-binary (#3765) xuba
• [PR] [AMORO-3754]failed to failover when only one node is alive in ha mode #3754 [amoro] via GitHub
  • Re: [PR] [AMORO-3754]failed to failover when only one node is alive in ha mode #3754 [amoro] via GitHub
  • Re: [PR] [AMORO-3754]failed to failover when only one node is alive in ha mode #3754 [amoro] via GitHub
  • Re: [PR] [AMORO-3754]failed to failover when only one node is alive in ha mode #3754 [amoro] via GitHub
  • Re: [PR] [AMORO-3754]failed to failover when only one node is alive in ha mode #3754 [amoro] via GitHub
• [I] [Subtask]: Supports the use of the default master-slave mode or the extended master-slave mode through configuration control [amoro] via GitHub
  • Re: [I] [Subtask]: Supports the use of the default master-slave mode or the extended master-slave mode through configuration control [amoro] via GitHub
  • Re: [I] [Subtask]: Supports the use of the default master-slave mode or the extended master-slave mode through configuration control [amoro] via GitHub
  • Re: [I] [Subtask]: Supports the use of the default master-slave mode or the extended master-slave mode through configuration control [amoro] via GitHub
• [I] [Bug]: LICENSE-BINARY lists snakeyaml-engine as BSD license - should be Apache license [amoro] via GitHub
  • Re: [I] [Bug]: LICENSE-BINARY lists snakeyaml-engine as BSD license - should be Apache license [amoro] via GitHub
  • Re: [I] [Bug]: LICENSE-BINARY lists snakeyaml-engine as BSD license - should be Apache license [amoro] via GitHub
• [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [PR] [Amoro-3762][Subtask] Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
• [I] [Subtask]: Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
  • Re: [I] [Subtask]: Change TableService to SPI mode to support expansion of other implementation methods. [amoro] via GitHub
• [I] [Bug]: set "self-optimizing.enabled=true" but table optimizing task keep pending [amoro] via GitHub
  • Re: [I] [Bug]: set "self-optimizing.enabled=true" but table optimizing task keep pending [amoro] via GitHub
  • Re: [I] [Bug]: set "self-optimizing.enabled=true" but table optimizing task keep pending [amoro] via GitHub
  • Re: [I] [Bug]: set "self-optimizing.enabled=true" but table optimizing task keep pending [amoro] via GitHub
  • Re: [I] [Bug]: set "self-optimizing.enabled=true" but table optimizing task keep pending [amoro] via GitHub
• [PR] [Improvement]: Introduce TableRuntimeFactory interface [amoro] via GitHub
  • Re: [PR] [Improvement]: Introduce TableRuntimeFactory interface [amoro] via GitHub
  • Re: [PR] [Improvement]: Introduce TableRuntimeFactory interface [amoro] via GitHub
  • Re: [PR] [Improvement]: Introduce TableRuntimeFactory interface [amoro] via GitHub
  • Re: [PR] [Improvement]: Introduce TableRuntimeFactory interface [amoro] via GitHub
• [I] [Improvement]: use table_identifier as cache for front-end list table [amoro] via GitHub
  • Re: [I] [Improvement]: use table_identifier as cache for front-end list table [amoro] via GitHub
  • Re: [I] [Improvement]: use table_identifier as cache for front-end list table [amoro] via GitHub
  • Re: [I] [Improvement]: use table_identifier as cache for front-end list table [amoro] via GitHub
• [I] [Improvement]: Optimize log output of SchedulingPolicy [amoro] via GitHub
  • Re: [I] [Improvement]: Optimize log output of SchedulingPolicy [amoro] via GitHub
• (amoro) branch master updated: [AMORO-3757] Configure ml for discussion to make .asf.yml notification happy jinsongzhou
• (amoro) branch master updated: [AMORO-3744] Add support for API Token service. jinsongzhou
• [PR] [AMORO-3757] Configure ml for discussion to make .asf.yml notification happy [amoro] via GitHub
  • Re: [PR] [AMORO-3757] Configure ml for discussion to make .asf.yml notification happy [amoro] via GitHub
• [I] [Feature]: Configure the discussion maillist target in .asf.yaml [amoro] via GitHub
  • Re: [I] [Feature]: Configure the discussion maillist target in .asf.yaml [amoro] via GitHub
• (amoro) branch master updated: [Improvement]: Optimize log output of SchedulingPolicy #3755 jinsongzhou
• [PR] [AMORO-3755][Improvement]: Optimize log output of SchedulingPolicy [amoro] via GitHub
  • Re: [PR] [AMORO-3755][Improvement]: Optimize log output of SchedulingPolicy [amoro] via GitHub
• [I] [Bug]: failed to failover when only one node is alive in ha mode [amoro] via GitHub
  • Re: [I] [Bug]: failed to failover when only one node is alive in ha mode [amoro] via GitHub
• [I] [Improvement]: enable configure session timeout for ha zookeeper [amoro] via GitHub
  • Re: [I] [Improvement]: enable configure session timeout for ha zookeeper [amoro] via GitHub
• (amoro) branch 0.8.1-rc1 updated: Revert "[AMORO-3540] Increase the precision of optimizing_status_start_time from s to ms. (#3542)" klion26
• (amoro) annotated tag v0.8.1-rc1 updated (bc906c099 -> e0bf9d7f3) klion26
• [I] [Bug]: Data inconsistency caused by switching between primary and backup nodes [amoro] via GitHub
  • Re: [I] [Bug]: Data inconsistency caused by switching between primary and backup nodes [amoro] via GitHub
  • Re: [I] [Bug]: Data inconsistency caused by switching between primary and backup nodes [amoro] via GitHub
  • Re: [I] [Bug]: Data inconsistency caused by switching between primary and backup nodes [amoro] via GitHub
  • Re: [I] [Bug]: Data inconsistency caused by switching between primary and backup nodes [amoro] via GitHub
  • Re: [I] [Bug]: Data inconsistency caused by switching between primary and backup nodes [amoro] via GitHub
  • Re: [I] [Bug]: Data inconsistency caused by switching between primary and backup nodes [amoro] via GitHub
• svn commit: r78902 - dev/incubator/amoro/0.8.1-incubating-RC1 klion26
• (amoro) branch 0.8.x updated: Revert "[AMORO-3540] Increase the precision of optimizing_status_start_time from s to ms. (#3542)" klion26
• [I] [Improvement]: The optimizer adds a cache of eq delete files to reduce repeated IO cost of eq delete files [amoro] via GitHub
  • Re: [I] [Improvement]: The optimizer adds a cache of eq delete files to reduce repeated IO cost of eq delete files [amoro] via GitHub
• svn commit: r78896 - dev/incubator/amoro klion26
• svn commit: r78895 - dev/incubator/amoro klion26
• svn commit: r78894 - release/incubator/amoro klion26
• svn commit: r78893 - dev/incubator/amoro klion26
• [PR] [hotfix] Update upgrade.sql after 0.8.1 release [amoro] via GitHub
  • Re: [PR] [hotfix] Update upgrade.sql after 0.8.1 release [amoro] via GitHub
  • Re: [PR] [hotfix] Update upgrade.sql after 0.8.1 release [amoro] via GitHub
• [PR] Update upgrade.sql for 0.8.1 release [amoro] via GitHub
  • Re: [PR] Update upgrade.sql for 0.8.1 release [amoro] via GitHub
  • Re: [PR] Update upgrade.sql for 0.8.1 release [amoro] via GitHub
• Re: [I] [Feature]: Support multi-instance AMS REST service [amoro] via GitHub
  • Re: [I] [Feature]: Support multi-instance AMS REST service [amoro] via GitHub
  • Re: [I] [Feature]: Support multi-instance AMS REST service [amoro] via GitHub
• Re: [I] [Feature]: Refactor AMS using function and process api [amoro] via GitHub
  • Re: [I] [Feature]: Refactor AMS using function and process api [amoro] via GitHub
  • Re: [I] [Feature]: Refactor AMS using function and process api [amoro] via GitHub
• (amoro) branch 0.8.1-rc1 created (now 2c79c4030) klion26
  • (amoro) 01/01: Bump version to 0.8.1-incubating klion26
• (amoro) branch 0.8.x updated (56b686abb -> 90c08aace) klion26
  • (amoro) 01/03: Add some third-party components imformation in the LICENSE (#3743) klion26
  • (amoro) 03/03: Remove ASF projects from NOTICE files (#3743) klion26
  • (amoro) 02/03: Fill binary NOTICE file (#3743) klion26
• (amoro) branch master updated (fbd1ee46d -> e3c16af3d) jinsongzhou
  • (amoro) 03/03: Remove ASF projects from NOTICE files jinsongzhou
  • (amoro) 01/03: Add some third-party components imformation in the LICENSE jinsongzhou
  • (amoro) 02/03: Fill binary NOTICE file jinsongzhou
• [I] [Improvement]: Manifest-driven and partition-aware data expiration [amoro] via GitHub
  • Re: [I] [Improvement]: Manifest-driven and partition-aware data expiration [amoro] via GitHub
  • Re: [I] [Improvement]: Manifest-driven and partition-aware data expiration [amoro] via GitHub
  • Re: [I] [Improvement]: Manifest-driven and partition-aware data expiration [amoro] via GitHub
• (amoro) branch master updated (7e9edbf41 -> fbd1ee46d) jinsongzhou
  • (amoro) 01/02: [AMORO-3734][Improvement]: Add operation/schemaId to Snapshot jinsongzhou
  • (amoro) 02/02: Addressed jinsongzhou
• (amoro) branch 0.8.x updated (7d2b88c99 -> 56b686abb) jinsongzhou
• Re: [I] [Bug]: java.lang.IllegalArgumentException: Row arity: 2, but serializer arity: 4 [amoro] via GitHub
  • Re: [I] [Bug]: java.lang.IllegalArgumentException: Row arity: 2, but serializer arity: 4 [amoro] via GitHub
  • Re: [I] [Bug]: java.lang.IllegalArgumentException: Row arity: 2, but serializer arity: 4 [amoro] via GitHub
• [PR] [AMORO-3747] Introducing a more general TableRuntime storage structure [amoro] via GitHub
  • Re: [PR] [AMORO-3747] Introducing a more general TableRuntime storage structure [amoro] via GitHub
  • Re: [PR] [AMORO-3747] Introducing a more general TableRuntime storage structure [amoro] via GitHub
  • Re: [PR] [AMORO-3747] Introducing a more general TableRuntime storage structure [amoro] via GitHub
  • Re: [PR] [AMORO-3747] Introducing a more general TableRuntime storage structure [amoro] via GitHub
  • Re: [PR] [AMORO-3747] Introducing a more general TableRuntime storage structure [amoro] via GitHub
  • Re: [PR] [AMORO-3747] Introducing a more general TableRuntime storage structure [amoro] via GitHub
  • Re: [PR] [AMORO-3747] Introducing a more general TableRuntime storage structure [amoro] via GitHub
  • Re: [PR] [AMORO-3747] Introducing a more general TableRuntime storage structure [amoro] via GitHub
• (amoro) branch master updated: [AMORO-3742] Fix errors in sql scripts (#3745) xuba
• [I] [Subtask]: Introducing a more general TableRuntime storage structure [amoro] via GitHub
  • Re: [I] [Subtask]: Introducing a more general TableRuntime storage structure [amoro] via GitHub
• (amoro) branch master updated: [hotfix] Fix doc error in displaying "Using Customized Encryption Method for Configurations" on admin guidance page (#3741) jinsongzhou
• Re: [I] [Bug]: The partition field of the mixed_hive table contains uppercase letters, which can lead to the erroneous deletion of Hive partitions when synchronizing data to Hive. [amoro] via GitHub
  • Re: [I] [Bug]: The partition field of the mixed_hive table contains uppercase letters, which can lead to the erroneous deletion of Hive partitions when synchronizing data to Hive. [amoro] via GitHub
  • Re: [I] [Bug]: The partition field of the mixed_hive table contains uppercase letters, which can lead to the erroneous deletion of Hive partitions when synchronizing data to Hive. [amoro] via GitHub

• Earlier messages
• Later messages