Petr Masopust
Petr Masopust
@jerryshao We have separate platform and customer apps. They are connected only through http proxy with authentication and authorization. There is no direct hdfs access, so we need upload apps...
My goal was small addition with minimal changes to current API. So far only batch request is enhanced with delayed flag plus 4 new methods for file uploads. First call...
1. yes - it is possible (see https://tools.ietf.org/html/rfc7578#section-4.3) but not very common. For better reliability it is better to split upload into separate calls (lack of reconnect support). I don't...
Imagine this scenario: 1. client uploads some file 2. client crashes 3. file is uploaded to hdfs but session is never started and file never deleted After some time hdfs...
Looks like Toree is only for interactive mode without uploads at all. JobServer has something like simple filesystem with upload and delete support.
Keeping old unused files is bad idea everywhere. New retention mechanism is possible but why not use something what is currently in use and working ? And if we go...
You almost exactly described this pull request. The only difference is between 1. and 3. where the most batch information are send in 1. and not 3.. 3. is only...
Are you really talking about complete API rework for batches and interactive sessions ? My goal was to keep current API as is, only with minimal backward compatible changes. I...
Hello Martin, no further progress from me - we decided to use another solution.
I am not authorized to post this information but it is commercial solution, not open source.