Skip to content

Conversation

@ligangty
Copy link
Member

The old way of indexing generation function is using a .index file as
cache for each changed directory to avoid full scan of the whole s3
bucket, this brings bunch of complicated steps, like recursive folder
scan and reading, and local file reading of .index to do merging. The
new way is using a new function to scan and retrieving the contents
in a single folder, which is cheap way to get the contents to avoid
full scan.

@coveralls
Copy link

coveralls commented Nov 29, 2021

Pull Request Test Coverage Report for Build 1529261724

  • 116 of 122 (95.08%) changed or added relevant lines in 3 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage decreased (-0.5%) to 82.04%

Changes Missing Coverage Covered Lines Changed/Added Lines %
charon/pkgs/npm.py 30 31 96.77%
charon/pkgs/indexing.py 62 67 92.54%
Files with Coverage Reduction New Missed Lines %
charon/storage.py 1 85.48%
Totals Coverage Status
Change from base Build 1521453882: -0.5%
Covered Lines: 1078
Relevant Lines: 1314

💛 - Coveralls

@lgtm-com
Copy link

lgtm-com bot commented Nov 29, 2021

This pull request introduces 2 alerts when merging 28224f6 into 1dbce0e - view on LGTM.com

new alerts:

  • 2 for Incomplete ordering

@ligangty
Copy link
Member Author

@shokakucarrier This is a proposal now to support changes in a new coming requirements in MMENG-2319. If you think it is not a correct change, let's hold it.

@ligangty ligangty changed the title Refactor: change indexing generation function [Proposal] Refactor: change indexing generation function Nov 30, 2021
@lgtm-com
Copy link

lgtm-com bot commented Nov 30, 2021

This pull request introduces 1 alert when merging 1c65138 into dabc485 - view on LGTM.com

new alerts:

  • 1 for Incomplete ordering

@lgtm-com
Copy link

lgtm-com bot commented Nov 30, 2021

This pull request introduces 1 alert when merging 8bbabe0 into ceea2f1 - view on LGTM.com

new alerts:

  • 1 for Incomplete ordering

@shokakucarrier
Copy link
Member

@ligangty using delimiter is a good idea, you we can merge this, do you need me to do further testing and potential fixing on this?

Copy link
Member

@shokakucarrier shokakucarrier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ligangty
Copy link
Member Author

ligangty commented Dec 2, 2021

@shokakucarrier Ok. No worry about testing. Next step we will do staging testing with this pr.

   The old way of indexing generation function is using a .index file as
   cache for each changed directory to avoid full scan of the whole s3
   bucket, this brings bunch of complicated steps, like recursive folder
   scan and reading, and local file reading of .index to do merging. The
   new way is using a new function to scan and retrieving the contents
   in a single folder, which is cheap way to get the contents to avoid
   full scan.
@ligangty ligangty changed the title [Proposal] Refactor: change indexing generation function Refactor: change indexing generation function Dec 2, 2021
@ligangty ligangty merged commit 3b57da8 into Commonjava:main Dec 2, 2021
@ligangty ligangty deleted the index branch December 2, 2021 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants