nacho.d.g
nacho.d.g
We have support for the sequence, iterator and object protocol right now, but don't have support for the mapping protocol. Would be a nice addition to have in the future....
Due to broadcasting and forwarding mechanisms is very possible nodes may be hit several times, from different peers, to replicate the same exact operation in the case of update notifications....
This is a general tracking issue to monitor the status of the different techniques that will help with clients behind NAT when it comes to establishing direct connection between peers....
In order to have better observability and enable performance analysis (specially in async context) swap "log" for "tracing (include a compatible sink for log dependencies to get debug output from...
The current implementation is a bit naive implementation and when propagating a join requests backtracks and waits for an answer from the request chain of all nodes it has been...
The scenario is such that when you subscribe initially, currently you are stuck with that peer. There is missing logic yet to recover subscriptions when the node you are subscribed...
In the future build with both Sqlite and RocksDB as possible backends (via feature) in order to compare behavior and performance characteristics. Probably we will want to stick with one,...
There are a couple of examples that won't work because the necessary data is not available: * file_read * parquet_column_read We should either provide a small sample with the tests...
For core RDD ops we understand those which spawn in the original Apache Spark from SparkContext and/or the base RDD class and friends: SC: - [x] range - [x] filter...
The idea here is to improve the way we currently handle the deployment of jobs. Initially the scope for this issue should be very modest: A binary application based on...