Flavio Junqueira

Results 10 issues of Flavio Junqueira

**Problem description** The controller assigns a server to own each segment container in a Pravega cluster. The server owns the container in the sense that it is responsible for executing...

area/segmentstore
version/0.3.0
kind/feature
status/needs-attention
priority/P2

**Problem description** ``` io.pravega.segmentstore.server.containers.StreamSegmentContainerTests > testAppendWithOffset FAILED java.lang.AssertionError: expected: but was: at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at io.pravega.test.common.AssertExtensions.assertEventuallyEquals(AssertExtensions.java:68) at io.pravega.test.common.AssertExtensions.assertEventuallyEquals(AssertExtensions.java:46) at io.pravega.segmentstore.server.containers.StreamSegmentContainerTests.checkAppendLeaks(StreamSegmentContainerTests.java:1907) at io.pravega.segmentstore.server.containers.StreamSegmentContainerTests.testAppendWithOffset(StreamSegmentContainerTests.java:772) ``` **Problem location**...

kind/bug
area/segmentstore
status/needs-attention
priority/P1
tag/flakeyTest

**Problem description** We need to make sure that calls to manipulate internal streams and segments directly are not available to users. For example, a user must not be able to...

area/security
kind/enhancement
area/controller
priority/P2
area/rest
area/reliability

**Problem description** The flink source implemented currently creates the pravega reader group before the flink job is submitted. Hence the flink client instance needs access to the controller and will...

We have a couple of instances of printing stack traces that seem arbitrary. They don't seem to be doing anything with respect to helping the user understand what has gone...

**Problem description** Fix Javadoc warnings currently showing up when building. **Problem location** Javadoc. **Suggestions for an improvement** Fix the Javadoc warnings.

We need to publish schema registry documentation either on github directly or pravega.io. It would be best to have it documented in pravega.io or at least a reference there.

documentation

**Problem description** In PR #2085, we have made changes to how we calculate the timeouts of txns. We need to document such changes so that developers can understand what to...

kind/enhancement
area/documentation
status/needs-attention
priority/P3
version/0.5.0

The current readme still points to zookeeper.apache.org.

I see that there has not been updates to this repository in the past two years, and I tried to access generated files as indicated in the README: https://logsbenchmark00.blob.core.windows.net/ but...