I agree that it seems completely fine to update the web version of the docs
after a release. What would not be fine is updating the downloadable package
for it without another vote (and another release number). When people voted on
a release, they voted that we should put up that package as
I've never thought that docs are strictly part of a release and can't be
updated outside of one. Javadoc jars are included in releases with jars,
but that's more because they are produced by the build and are tied to the
source code. There is plenty of other documentation that isn't normally
Hi,
Thank you for your reply!
You got it right! I am trying to run multiple streams using the same
consumer, so that I can distribute different partitions among different
instances of the consumer group. I donĀ¹t want to provide the list of
partitions in createDirectStream API. If I do that then
Can you explain in more detail what you mean by "distribute Kafka
topics among different instances of same consumer group"?
If you're trying to run multiple streams using the same consumer
group, it's already documented that you shouldn't do that.
On Thu, Jun 8, 2017 at 12:43 AM, Rastogi, Pankaj
+1 from me. Felix et al indicated that the various "2.2" JIRAs had no
further actions. I retargeted most of the other 2.2.0-targeted JIRAs that
didn't seem like they're must-do. We have no Blockers and I'm not aware of
any changes that must be in the 2.2 release that aren't.
These are the only
Thanks Sai !
I have created a Jira Bug:
https://issues.apache.org/jira/browse/SPARK-21013
Regards n Thanks
Hari
mob: +1 813-510-8215
On Wed, Jun 7, 2017 at 11:44 PM, Saisai Shao wrote:
> Yes, currently if log is aggregated, then accessing through UI is not
> worked,
+1 non-binding
Tested on macOS Sierra, Ubuntu 16.04
test suite includes various test cases including Spark SQL, ML,
GraphFrames, Structured Streaming
On Wed, Jun 7, 2017 at 9:40 PM vaquar khan wrote:
> +1 non-binding
>
> Regards,
> vaquar khan
>
> On Jun 7, 2017 4:32
Yes, currently if log is aggregated, then accessing through UI is not
worked, you can create a JIRA to improve this if you would like to.
On Thu, Jun 8, 2017 at 1:43 PM, ckhari4u wrote:
> Hey Guys,
>
> I am hitting the below issue when trying to access the STDOUT/STDERR logs