BlobCity DB joins Hacktoberfest 2019

BlobCity DB is proud to join Hacktoberfest. We are here to help you contribute into our next generation database, with an opportunity to forever change the way enterprises store and process their data.

If you have never contributed to an open source project, but would like to contribute, then Hacktoberfest is the best time of the year to start your open source journey.

What is Hacktoberfest?

It is a month long celebration of open source, celebrated in the month of October. Hacking + October + Fest = Hacktoberfest.

During Hacktoberfest, open source project maintainers, guide first time contributors to start contributing in their respective repositories. Guidance includes offering understanding of an open source project, and helping with Github Pull Requests and helping abide by the best practices of the repository. In return, the contributor stands a chance to win some limited edition Hacktoberfest T-Shits from the organisers of the fest, which is DigitalOcean and Dev.

What is BlobCity DB

BlobCity DB is a blazing fast open source NoSQL database. It is commonly used as a Data Lake solution. We call it a database as it is more of a database than a Data Lake, but can pretty much do anything a Data Lake does. BlobCity DB specialises in storing 17 formats of data. It is ACID compliant, supports SQL, offers Java & Scala based stored procedures and allows storing of data on disk and in-memory.

How to Participate

First register on Hacktoberfest, choose an open source project, choose an open issue from within the open source project, solve the issue and submit your code in the form of a pull request. If the maintainer of the repository accepts your pull requests, you will have a qualified entry into the contest. A pull request being accepted is not important, but it should not be marked as inappropriate by the repository maintainer.

1. Register on Hacktoberfest

Register on Hacktoberfest with your Github account. If you don’t have a Github account, you can make one for free. Setup your Github profile, so that repository maintainers can know your background when you send them a pull request.


2. Choose an Issue

You can choose an open issue from BlobCity DB and start working on it. We have issues specially marked for Hacktoberfest. You may choose issues from any other open source project too.


3. Connect with us

We are happy to help in getting you started. Join our Slack community and ask us anything on Hacktoberfest & BlobCity DB.


4. Fork the repository

Once you have decided you want to solve a particular issue, fork the repository on Github.

5. Resolve & Send Pull Request

Now you can choose an issue of your choice, and work on it. Test your new code, and commit it to your fork once your are done. You can now submit your work by generating a pull requests from your fork to the main repository. Now hope that the maintainer of the repository likes your work and accepts your pull request. Remember, it is not necessary for your pull request to be merged for you to have a qualified entry in Hacktoberfest.

That’s how simple it is. Choose your open source project and start contributing today. It’s time to give back to the open source we all love 🙂

Delete large files from historic commits in Git

git filter-branch --index-filter 'git rm -r --cached --ignore-unmatch <file>' HEAD

It can be tricky to remove a large file from git that goes several commits in the history, specifically when there are other source files in the same commits that you want to retain. The above command will do just this for you.

Caution: You will land up changing the hashes of all your commits that have the file in it. There maybe a massive conflict resolution that you may have to do after this command, but if you have to remove the file, this might just be the best way to get it done.

You are likely required to make this change, when Git is preventing pushes due to exceeding the file limit.

remote: error: File my_binary.tar.gz is 300.08 MB; this exceeds GitHub's file size limit of 100.00 MB

Use the git filter-branch command mentioned at top by replacing <file> with the location within the repository of the file you want to delete. You can also specify a folder if a complete folder is to be deleted.

Before you run the command make sure the <file> is currently deleted from the current branch. Also ensure that the delete of the file is committed within the repository even if the delete operation could not be pushed to remote.

Example Run

git filter-branch --index-filter 'git rm -r --cached --ignore-unmatch my_binary.tar.gz' HEAD
Rewrite f1824be80ff0ff2bd27064094245288252fc479a (71/118) (3 seconds passed, remaining 1 predicted)    rm 'my_binary.tar.gz'
Rewrite dc4a60df97e753e98804cc432339a6b4675ba9e7 (71/118) (3 seconds passed, remaining 1 predicted)    rm 'my_binary.tar.gz'
Rewrite 09a87540b07fa5ba0c9dc0ba1861720f51cb5e98 (71/118) (3 seconds passed, remaining 1 predicted)    rm 'my_binary.tar.gz'
Rewrite e1be7aa558591bb06049808161fca0c97071165c (71/118) (3 seconds passed, remaining 1 predicted)    rm 'my_binary.tar.gz'
Rewrite 1925fa84c42e379f8dd1d44cbda18da52ac5091e (71/118) (3 seconds passed, remaining 1 predicted)    rm 'my_binary.tar.gz'
Rewrite b96b54fecbf7dec09274ef30990995bf4a97288a (71/118) (3 seconds passed, remaining 1 predicted)    rm 'my_binary.tar.gz'
Rewrite 75d364753f247d983e83ab408eaa0af2f2fff5a1 (71/118) (3 seconds passed, remaining 1 predicted)    rm 'my_binary.tar.gz'
Rewrite b839c3c1dd0e6277083b74801629e9138591be49 (95/118) (4 seconds passed, remaining 0 predicted)    
Ref 'refs/heads/master' was rewritten

Post running the command, attempt a push to remote. It will very likely not work. If it does not it is expected. Take a pull, resolve any CONFLICT that shows up, make sure the file you deleted is still deleted and if not delete it from your folder, commit the changes and push. Your push should now work.