Congxian Qiu

Results 85 comments of Congxian Qiu

----------------------------------------------------- AMORO-3194(3212) 7081bbcfe Amoro-3196(3203) 5027abe2 AMORO-3111(3115) 292111f6e AMORO-3110(3113) 9877c206e AMORO-3145(3185) b52f64d778 (3152) 68bda4820 AMORO-3153(3154) 8207efcd4c AMORO-3141(3142) a8b2ff577e AMORO-3132(3133) 79f1beaf8 AMORO-3110(3130) 5adbfbf6f AMORO-3128(3129) 2bf68a19d AMORO-3098(3098) bc0034a51 AMORO-2555(3058) 706630055 Hotfix(3069) a55010357 AMORO-3076...

#3218 was introduced by #2914 ,and #2914 did not located in 0.7.x so we dont need to merge #3218 into 0.7.x

---------------------------------------------------- (3284) 27c4cc08f4ac48c8a89210a36db4e2bd5d761350 AMORO-2870(3175) 6982a3289aabb78328dbbb4bfeceee61122256b9 AMORO-3239(3240) cc29688004ecd0b24b5bbafaa2f8326cb19a087e AMORO-3242(3243) 3e17628b8ab304aae52d605e4610b6156a1ec007 AMORO-3172(3173) 6ed81626026ee6ff2fd5c02fe087225aecd80066 AMORO-3228(3229) a1812818ff247ff6216a70234c38a8f4dd0a54fe (3227) dc8f32fb849dcec53e6ddd0d5ed9193137825cc7 (3222) 222d816efdfe405713981db76a66c33cfa0d295d AMORO-3224(3225) 222d816efdfe405713981db76a66c33cfa0d295d AMORO-3110(3223) a2bc71ab7360760035b55ade676dcab2d90e6b74 (3219) hotfix c879fdbef59893eb937d3f8c785d0aaf169c3958 (3215) hotfix acf3db1f47e4d7305a7ab210870cc1de1296335b

# Improvements: - Support graceful shutdown for AMS #3057 - Prevent the table name from being truncated prematurely #3077 - Load log4j configuration file from AMORO_CONF_DIR #3098 - Make yarn...

Close this issue as 0.7.1 has been released. - [release note for 0.7.1](https://github.com/apache/amoro/releases/tag/v0.7.1-incubating) - [announce ml for 0.7.1](https://lists.apache.org/thread/62fwwplzgdlg57oyd3ngc388gvbmw8sb)

LGTM for the new change, as the change only changes the `planTime` generate logic, and the `planTime`, which was generated in a single thread, the change here avoids the duplication...

Currently, this is a draft version just a better discussion. the open questions are 1. Do we need to include the `table format` in what we return to the front...

@baiyangtx thanks for the review, the bottle-neck here is not the cost of the sort, but we retrieved too much data from DB, the solution here wants to limit the...