Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapt analyzer to actually use Spark rather than just collect data from HDFS #2

Open
gubser opened this issue Jul 1, 2016 · 0 comments

Comments

@gubser
Copy link
Owner

gubser commented Jul 1, 2016

Currently the analyzer just iterates over the raw data and applies the analysis in the local python interpreter. Instead it should run it in Spark, the thing i have to think about is what happens if a file is corrupt. Data corruption should not raise an analyzer error, instead it should notify the core that it is not happy with the data. (Also see mami-project/pto-core#20)

Example: download the ipfix file from the measurement server without having stopped QoF beforehand. the ipfix reader will raise an exception because there is no end signature(?) in the file.

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

No branches or pull requests

1 participant