Wangyuan Zhang <wyzhang@google.com>: Author Summary

Builds triggered by Wangyuan Zhang <wyzhang@google.com>

Builds triggered by an author are those builds which contains changes committed by the author.
34
7 (21%)
27 (79%)

Breakages and fixes

Broken means the build has failed but the previous build was successful.
Fixed means that the build was successful but the previous build has failed.
4 (12% of all builds triggered)
2 (6% of all builds triggered)
-2
Build Completed Code commits Tests
CDAP › DUT › #3453 1 day ago
[CDAP-18627] Split preview leveldb store into 2 stores.              One for data+metadata and the other for pending
Why:
Splitting into separate levelDB stores to minimize any potential
slow seek or scan operations, since this store has high deletion
rate, thus producing lots of deletion markers or tombstones.
As a result, it is fairly easy to cause very slow seek or scan
(e.g. calling seekToStart or using iterator.next() to find target row)
during implementation. Splitting minimizes/reduces the slowness.
Furthermore, a followup PR to enable compaction on these levelDB
will allow us compacting away these deletion markers frequently,
thus speeding up access operations.
3127 passed
CDAP › RUT › #1637 1 day ago
[CDAP-18627] Split preview leveldb store into 2 stores.              One for data+metadata and the other for pending
Why:
Splitting into separate levelDB stores to minimize any potential
slow seek or scan operations, since this store has high deletion
rate, thus producing lots of deletion markers or tombstones.
As a result, it is fairly easy to cause very slow seek or scan
(e.g. calling seekToStart or using iterator.next() to find target row)
during implementation. Splitting minimizes/reduces the slowness.
Furthermore, a followup PR to enable compaction on these levelDB
will allow us compacting away these deletion markers frequently,
thus speeding up access operations.
3127 passed
CDAP › DRC › #5618 1 day ago
[CDAP-18627] Split preview leveldb store into 2 stores.              One for data+metadata and the other for pending
Why:
Splitting into separate levelDB stores to minimize any potential
slow seek or scan operations, since this store has high deletion
rate, thus producing lots of deletion markers or tombstones.
As a result, it is fairly easy to cause very slow seek or scan
(e.g. calling seekToStart or using iterator.next() to find target row)
during implementation. Splitting minimizes/reduces the slowness.
Furthermore, a followup PR to enable compaction on these levelDB
will allow us compacting away these deletion markers frequently,
thus speeding up access operations.
Testless build
CDAP › BPP › #1886 1 day ago
[CDAP-18627] Split preview leveldb store into 2 stores.              One for data+metadata and the other for pending
Why:
Splitting into separate levelDB stores to minimize any potential
slow seek or scan operations, since this store has high deletion
rate, thus producing lots of deletion markers or tombstones.
As a result, it is fairly easy to cause very slow seek or scan
(e.g. calling seekToStart or using iterator.next() to find target row)
during implementation. Splitting minimizes/reduces the slowness.
Furthermore, a followup PR to enable compaction on these levelDB
will allow us compacting away these deletion markers frequently,
thus speeding up access operations.
Testless build
CDAP › DUT › #3451 1 week ago
[CDAP-18626] Revive artifact-fetching-and-caching-WITHOUT-unpacking API
Why:
To allow preview runner running with restricted permission (i.e.
no permission to access artifacts on distributed file system or
metadata in external database), we need an API for preview runner
to fetch and cache artifact.

What:
Add back the APIs for ArtifactLocalizer to fetch artifact jar.
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
address comment
3124 passed
CDAP › RUT › #1635 1 week ago
address comment
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
[CDAP-18626] Revive artifact-fetching-and-caching-WITHOUT-unpacking API
Why:
To allow preview runner running with restricted permission (i.e.
no permission to access artifacts on distributed file system or
metadata in external database), we need an API for preview runner
to fetch and cache artifact.

What:
Add back the APIs for ArtifactLocalizer to fetch artifact jar.
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
3124 passed
CDAP › BPP › #1883 1 week ago
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
address comment
[CDAP-18626] Revive artifact-fetching-and-caching-WITHOUT-unpacking API
Why:
To allow preview runner running with restricted permission (i.e.
no permission to access artifacts on distributed file system or
metadata in external database), we need an API for preview runner
to fetch and cache artifact.

What:
Add back the APIs for ArtifactLocalizer to fetch artifact jar.
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
Testless build
CDAP › DRC › #5615 1 week ago
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
[CDAP-18626] Revive artifact-fetching-and-caching-WITHOUT-unpacking API
Why:
To allow preview runner running with restricted permission (i.e.
no permission to access artifacts on distributed file system or
metadata in external database), we need an API for preview runner
to fetch and cache artifact.

What:
Add back the APIs for ArtifactLocalizer to fetch artifact jar.
address comment
Testless build
CDAP › RUT › #1634 1 week ago
[CDAP-18627] LevelDB increasing default block size 1K -> 8K
Why:
Larger block size is preferred for scan access pattern.
This is the typical access pattern in CDAP.
1 of 1272 failed
CDAP › DUT › #3450 1 week ago
[CDAP-18627] LevelDB increasing default block size 1K -> 8K
Why:
Larger block size is preferred for scan access pattern.
This is the typical access pattern in CDAP.
1 of 2187 failed
Build Completed Code commits Tests
CDAP › RUT › #1634 1 week ago
[CDAP-18627] LevelDB increasing default block size 1K -> 8K
Why:
Larger block size is preferred for scan access pattern.
This is the typical access pattern in CDAP.
1 of 1272 failed
CDAP › DUT › #3450 1 week ago
[CDAP-18627] LevelDB increasing default block size 1K -> 8K
Why:
Larger block size is preferred for scan access pattern.
This is the typical access pattern in CDAP.
1 of 2187 failed
CDAP › DUT › #2808 1 year ago
Fixing a bug in preferences merge method (child take precedence over parent).
Adding test cases for this case
2 of 2654 failed
CDAP › RUT › #1005 1 year ago
Fixing a bug in preferences merge method (child take precedence over parent).
Adding test cases for this case
2656 passed
Build Completed Code commits Tests
CDAP › DUT › #3451 1 week ago
[CDAP-18626] Revive artifact-fetching-and-caching-WITHOUT-unpacking API
Why:
To allow preview runner running with restricted permission (i.e.
no permission to access artifacts on distributed file system or
metadata in external database), we need an API for preview runner
to fetch and cache artifact.

What:
Add back the APIs for ArtifactLocalizer to fetch artifact jar.
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
address comment
3124 passed
CDAP › RUT › #1635 1 week ago
address comment
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
[CDAP-18626] Revive artifact-fetching-and-caching-WITHOUT-unpacking API
Why:
To allow preview runner running with restricted permission (i.e.
no permission to access artifacts on distributed file system or
metadata in external database), we need an API for preview runner
to fetch and cache artifact.

What:
Add back the APIs for ArtifactLocalizer to fetch artifact jar.
[CDAP-18627] Enable levelDB periodic compaction (once per 7 days)              Also randomize compactions timings of tables.
Why:
periodic compaction allows us to recycle disk space and discard
tombstones/deletion-markers. This can improve levelDB access latency.
3124 passed