[jira] [Updated] (RATIS-63) Add NOTICE.txt
[ https://issues.apache.org/jira/browse/RATIS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated RATIS-63: - Attachment: r63_20170412.patch It seems that we only need a very basic NOTICE file as shown in the following patch. Will double check. r63_20170412.patch > Add NOTICE.txt > -- > > Key: RATIS-63 > URL: https://issues.apache.org/jira/browse/RATIS-63 > Project: Ratis > Issue Type: Sub-task >Reporter: Tsz Wo Nicholas Sze >Assignee: Tsz Wo Nicholas Sze > Attachments: r63_20170412.patch > > > According to [Licensing > Documentation|http://www.apache.org/legal/release-policy.html#licensing-documentation], > we need a NOTICE file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RATIS-56) Update project version to 0.1.0-alpha
[
https://issues.apache.org/jira/browse/RATIS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965284#comment-15965284
]
Tsz Wo Nicholas Sze commented on RATIS-56:
--
Just have tried. The following command works well.
{code}
mvn versions:set -DnewVersion=0.1.0-alpha
{code}
(Note that there were typos in previous comments: "versons" should be
"versions".)
> Update project version to 0.1.0-alpha
> -
>
> Key: RATIS-56
> URL: https://issues.apache.org/jira/browse/RATIS-56
> Project: Ratis
> Issue Type: Sub-task
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
> Attachments: r56_20170330.patch, r56_20170402.patch
>
>
> We may use the following command to update the project version from
> 0.1-SNAPSHOT to 0.1.0-alpha.
> {code}
> find . -name pom.xml | xargs sed -i.old "s/0.1-SNAPSHOT/0.1.0-alpha/g"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RATIS-67) BUILDING.md file is not correct
[
https://issues.apache.org/jira/browse/RATIS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965281#comment-15965281
]
Tsz Wo Nicholas Sze commented on RATIS-67:
--
Hi [~khmarbaise], I must have missed something since {{mvn package
-DskipTests}} does work for me. How could I reproduce the bug?
I noticed that you were using your own nexus server
({{http://localhost:8081/nexus/..}}). Not sure if it is related.
> BUILDING.md file is not correct
> ---
>
> Key: RATIS-67
> URL: https://issues.apache.org/jira/browse/RATIS-67
> Project: Ratis
> Issue Type: Bug
>Affects Versions: 0.1.0-alpha
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 0.1.0-alpha
>
>
> The {{BUILDING.md}} file claims to build RATIS for the first time via:
> {code}
> mvn package -DskipTests
> {code}
> which simply fails with the following output:
> {code}
> [ERROR] Failed to execute goal on project ratis-hadoop-shaded: Could not
> resolve dependencies for project
> org.apache.ratis:ratis-hadoop-shaded:jar:0.1-SNAPSHOT: Failure to find
> org.apache.hadoop:hadoop-common:jar:3.0.0-alpha1 in
> http://localhost:8081/nexus/content/groups/public was cached in the local
> repository, resolution will not be reattempted until the update interval of
> nexus has elapsed or updates are forced -> [Help 1]
> {code}
> This looks like those dependencies are used instead of being dependencies
> defined by {{true
[jira] [Updated] (RATIS-70) Separate term/index/offset and log entry content in LogSegment
[
https://issues.apache.org/jira/browse/RATIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated RATIS-70:
---
Attachment: RATIS-70.001.patch
Update the patch: {{RaftLog#getEntries}} is currently only used by LeaderState
to check the term/index/configuration. Thus we do not really need to get the
log entries and returning TermIndex[] should be enough.
> Separate term/index/offset and log entry content in LogSegment
> --
>
> Key: RATIS-70
> URL: https://issues.apache.org/jira/browse/RATIS-70
> Project: Ratis
> Issue Type: Sub-task
>Reporter: Jing Zhao
>Assignee: Jing Zhao
> Attachments: RATIS-70.000.patch, RATIS-70.001.patch
>
>
> The current RaftLogCache consists of LogSegment, and logSegment consists of
> log entries. Instead of directly storing all the log entries, we should
> separate the term/index/offset information and the entry content information.
> The former part is more like the index information and can be always kept in
> the memory. The entry content part can later be evicted from the memory based
> on eviction policies.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RATIS-70) Separate term/index/offset and log entry content in LogSegment
[ https://issues.apache.org/jira/browse/RATIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated RATIS-70: --- Attachment: (was: RATIS-70.000.patch) > Separate term/index/offset and log entry content in LogSegment > -- > > Key: RATIS-70 > URL: https://issues.apache.org/jira/browse/RATIS-70 > Project: Ratis > Issue Type: Sub-task >Reporter: Jing Zhao >Assignee: Jing Zhao > Attachments: RATIS-70.000.patch > > > The current RaftLogCache consists of LogSegment, and logSegment consists of > log entries. Instead of directly storing all the log entries, we should > separate the term/index/offset information and the entry content information. > The former part is more like the index information and can be always kept in > the memory. The entry content part can later be evicted from the memory based > on eviction policies. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RATIS-70) Separate term/index/offset and log entry content in LogSegment
[ https://issues.apache.org/jira/browse/RATIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated RATIS-70: --- Attachment: RATIS-70.000.patch Rebase the patch. > Separate term/index/offset and log entry content in LogSegment > -- > > Key: RATIS-70 > URL: https://issues.apache.org/jira/browse/RATIS-70 > Project: Ratis > Issue Type: Sub-task >Reporter: Jing Zhao >Assignee: Jing Zhao > Attachments: RATIS-70.000.patch > > > The current RaftLogCache consists of LogSegment, and logSegment consists of > log entries. Instead of directly storing all the log entries, we should > separate the term/index/offset information and the entry content information. > The former part is more like the index information and can be always kept in > the memory. The entry content part can later be evicted from the memory based > on eviction policies. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
