Add ETL process to compress relevant data #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Due to many requests being captured, the login_address table grows quickly on large installations. However, the individual rows are not required for the training. As long as we know which (ip,uid) has been used first/last, we can separate training from test data while keeping the database compact. Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to many requests being captured, the login_address table grows quickly
on large installations. However, the individual rows are not required for the
training. As long as we know which (ip,uid) has been used first/last, we can
separate training from test data while keeping the database compact.
This will migrate and compress the existing data in batches of 25k rows per hour.
To my defense: I know this way of transforming the data is inefficient. I wish I could use the query builder to do it all in SQL and thuse don't pipe the data through php, but I couldn't get that working.