Closed shubhraneel closed 3 years ago
Hello @shubhraneel! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers:
This PR if merged will introduce the following changes
db
container shall be executed automatically again (if testing the function Bitap we need to run install.sh
everytime a change is made to Bitap, including this time)mariadb-udf
instead of mariadb:latest
This is some excellent work! I'll review it tonight.
@shubhraneel Please work on these changes. You are doing great.
I have a doubt. Since I have learned Docker recently, I may be wrong. If I use build: ./mariadb-udf-docker
, it builds a new image and then a container but the Makefile in mariadb-udf-docker
already creates an image named mariadb-udf
so I thought I should use that image created by Makefile itself.
Also, in case you are having a problem where the function does not work, I think deleting the database or using a new folder for the database while running install.sh works.
@shubhraneel I believe the best course of action will be not to build the image in the install.sh
script. Just run the makefile locally and commit bitap.so
. In this way, you won't require to compile it in user's computer and the build can happen directly.
It is better to keep the whole stack in a single docker-compose file. Otherwise all images except the db one will be properly tagged with iqps_
prefix.
One other way is to (and I believe it is better) is to just compile the .so file using the make
call in the install.sh
file: make bitap.so -C mariadb-udf-docker
I removed the build
command from the Makefile. I tested it and it is working. That way the redundant image is not created.
The PR looks good to me! Merging!
Written the Bitap function in C. Not yet integrated or tested with MySQL but tested it with words input by the user.