Closed X-czh closed 4 years ago
If no one has started working on storing flow results yet, I can take care of it.
Can someone work on porting a newer Hadoop/Spark/HBase version?
Can someone work on porting a newer Hadoop/Spark/HBase version?
What does porting mean? I mean, from my understanding, to port to newer version in this repo, we just need to download the latest version of Hadoop/Spark/HBase and put them in /app
folder, along with modifying hard-coded version in the source code of acai
. Are there other tasks to do to port a newer version?
Ideally you are right.
but Soot/FD could break and you will need to fix the problems.
Ideally you are right.
but Soot/FD could break and you will need to fix the problems.
Got it, and I'll have a try on porting hadoop first (not sure whether my PC memory is sufficient to run Soot on HBase/Spark)
Ideally you are right.
but Soot/FD could break and you will need to fix the problems.
Got it, and I'll have a try on porting hadoop first (not sure whether my PC memory is sufficient to run Soot on HBase/Spark)
I'll do the porting since I have access to the VM.
Ideally you are right. but Soot/FD could break and you will need to fix the problems.
Got it, and I'll have a try on porting hadoop first (not sure whether my PC memory is sufficient to run Soot on HBase/Spark)
I'll do the porting since I have access to the VM.
Thanks Zhanghao, can you have a try on porting Spark? I have successfully ported Hadoop but got stuck by a problem encountered when running soot on latest version of Spark. I wonder whether you will meet the same problem.
@leafeonia please post the problems you encountered and was not able to solve, instead of asking others to try again.
Also, @X-czh please create a separate issue for the porting instead of abusing the meeting minutes.
@leafeonia please post the problems you encountered and was not able to solve, instead of asking others to try again.
Also, @X-czh please create a separate issue for the porting instead of abusing the meeting minutes.
Thanks for suggestion, I have posted the problem in issue #4
Data types, case insensitivity, unused parameters are easy to check, we'll start with implementing them. We need to think about it more concretely by inspecting the flow/source code.
We need to figure out what kind of checking codes are there first to check inconsistency regarding checking code.
We need to think about how to check inconsistency regarding units. Manual labeling of params/APIs might be needed.
Need to find a way to store flow results in file to avoid rerunning Acai every time we run ccc. Each type of inconsistency checking will be implemented in a separate pass.