commits  

Messages by Thread

• (amoro-site) branch improve_release_guide deleted (was 27412ba) klion26
• Re: [I] [Improvement]: Use Duration unit with Self-optimizing Configurations [amoro] via GitHub
  • Re: [I] [Improvement]: Use Duration unit with Self-optimizing Configurations [amoro] via GitHub
  • Re: [I] [Improvement]: Use Duration unit with Self-optimizing Configurations [amoro] via GitHub
• (amoro) branch master updated: [AMORO-3698] Remove Flink 1.15 modules (#3771) jinsongzhou
• [I] [Subtask]: The "bucket_id" field is added to the table_identifier table to support balanced table partitioning in master-slave mode. [amoro] via GitHub
  • Re: [I] [Subtask]: add "bucket_id" field to the table_identifier table to support balanced table partitioning in master-slave mode. [amoro] via GitHub
• [I] [Feature]: Save the last completion time of the executor cleanup [amoro] via GitHub
  • Re: [I] [Feature]: Save the last completion time of the executor cleanup [amoro] via GitHub
• Re: [I] [Improvement]: Optimizing the RestAPI efficiency [amoro] via GitHub
  • Re: [I] [Improvement]: Optimizing the RestAPI efficiency [amoro] via GitHub
  • Re: [I] [Improvement]: Optimizing the RestAPI efficiency [amoro] via GitHub
• [PR] Fix the download url for source. [amoro-site] via GitHub
  • Re: [PR] Fix the download url for source. [amoro-site] via GitHub
  • Re: [PR] Fix the download url for source. [amoro-site] via GitHub
• [PR] Enhance the release guide for the web release procedure [amoro-site] via GitHub
  • Re: [PR] Enhance the release guide for the web release procedure [amoro-site] via GitHub
  • Re: [PR] Enhance the release guide for the web release procedure [amoro-site] via GitHub
• (amoro-site) branch 0.8.1 updated: Fix the download url for source. (#62) klion26
• (amoro-site) branch asf-site updated: deploy: c0d20a92be6e1426c205951c6206142484c1e83c github-bot
• (amoro-site) branch master updated: Fix the download url for source. (#62) klion26
• (amoro-site) branch enhance_release_guide updated (0d616e6 -> 0406d63) klion26
• (amoro-site) branch enhance_release_guide created (now 0d616e6) klion26
  • (amoro-site) 01/01: Enhance the release guide for the web release procedure klion26
• [PR] [Improvement] Implement manifest-driven data expiration [amoro] via GitHub
  • Re: [PR] [Improvement] Implement manifest-driven data expiration [amoro] via GitHub
  • Re: [PR] [Improvement] Implement manifest-driven data expiration [amoro] via GitHub
  • Re: [PR] [Improvement] Implement manifest-driven data expiration [amoro] via GitHub
  • Re: [PR] [Improvement] Implement manifest-driven data expiration [amoro] via GitHub
• (amoro-site) branch 0.8.1 created (now ab704e3) klion26
• (amoro-site) branch asf-site updated: deploy: ab704e3c0bc1bcfb932b3cf24bf48a52177edd79 github-bot
  • (amoro-site) branch asf-site updated: deploy: ab704e3c0bc1bcfb932b3cf24bf48a52177edd79 github-bot
• (amoro-site) branch master updated (3caed74 -> 2d67605) jinsongzhou
  • (amoro-site) 01/01: Merge pull request #60 from apache/improve_release_guide jinsongzhou
• [PR] [AMORO-3778] Add release yml to auto generate the release note [amoro] via GitHub
  • Re: [PR] [AMORO-3778] Add release yml to auto generate the release note [amoro] via GitHub
  • Re: [PR] [AMORO-3778] Add release yml to auto generate the release note [amoro] via GitHub
  • Re: [PR] [AMORO-3778] Add release yml to auto generate the release note [amoro] via GitHub
  • Re: [PR] [AMORO-3778] Add release yml to auto generate the release note [amoro] via GitHub
  • Re: [PR] [AMORO-3778] Add release yml to auto generate the release note [amoro] via GitHub
• [PR] [AMORO-SITE-59] Improve the release guide [amoro-site] via GitHub
  • Re: [PR] [AMORO-SITE-59] Improve the release guide [amoro-site] via GitHub
  • Re: [PR] [AMORO-SITE-59] Improve the release guide [amoro-site] via GitHub
• [PR] Release Apache amoro 0.8.1-incubating [amoro-site] via GitHub
  • Re: [PR] Release Apache amoro 0.8.1-incubating [amoro-site] via GitHub
• (amoro) annotated tag v0.8.1-incubating updated (bc906c099 -> 22d04cf3c) klion26
• Re: [I] [Feature]: Enable catalog-level default properties storing into underlying tables within a unified catalog [amoro] via GitHub
  • Re: [I] [Feature]: Enable catalog-level default properties storing into underlying tables within a unified catalog [amoro] via GitHub
• [PR] [AMORO-3775] Add support for pluggable refresh event 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
  • 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

• Earlier messages
• Later messages