[
https://issues.apache.org/jira/browse/IGNITE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287041#comment-14287041
]
Semen Boikov commented on IGNITE-110:
-
Need to keep SKIP_STORE functionality:
- add me
[
https://issues.apache.org/jira/browse/IGNITE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Setrakyan reassigned IGNITE-97:
---
Assignee: Dmitriy Setrakyan (was: Alexey Kuznetsov)
> Need to add LICENSE and NOTICE
[
https://issues.apache.org/jira/browse/IGNITE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286624#comment-14286624
]
Dmitriy Setrakyan edited comment on IGNITE-59 at 1/22/15 12:23 AM:
--
[
https://issues.apache.org/jira/browse/IGNITE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-97:
--
Assignee: Alexey Kuznetsov
> Need to add LICENSE and NOTICE files
>
[
https://issues.apache.org/jira/browse/IGNITE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286624#comment-14286624
]
Dmitriy Setrakyan commented on IGNITE-59:
-
Sergey,
Now, after reviewing the API, I
What other guys said: if you need a version docs - you keep them as a part of
the release and link to the it via the website.
E.g. you always can have the 'latest' link pointing to the last released bits
with the greatest docs in it. The website can point to the latest location as
the current doc
I believe we want to keep copy of the version docs in the website SVN?
You can take a look at Flink website example [1].
So it splits the doc into generic information, stored in that svn, and
release specific that stick with src [2] .
For each release we add versioned doc in the SVN "site/docs"
[
https://issues.apache.org/jira/browse/IGNITE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov reassigned IGNITE-70:
---
Assignee: Yakov Zhdanov
> Documentation links for Ignite lead to GridGain site
> -
On 21.01.2015 21:58, Dmitriy Setrakyan wrote:
> On Wed, Jan 21, 2015 at 12:52 PM, Branko Čibej wrote:
>
>> On 21.01.2015 21:18, Dmitriy Setrakyan wrote:
>>> Additionally, I wanted to find out if any one has any experience having
>>> "versioned" documentation. For example, in GridGain, every time w
[
https://issues.apache.org/jira/browse/IGNITE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov reassigned IGNITE-76:
---
Assignee: Yakov Zhdanov
> CME in tx map with optimistic txs
>
[
https://issues.apache.org/jira/browse/IGNITE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov reassigned IGNITE-96:
---
Assignee: Yakov Zhdanov
> Need To remove all extra methods from cache entry according to JCach
Cool, thanks for sharing the update.
On Wed, Jan 21, 2015 at 9:54 AM, Dmitriy Setrakyan
wrote:
> We have been assigned a new Jira workflow which has "Patch Available"
> status. This allows us to submit any ticket for review by a committer and
> flipping the status to "Patch Available". The commit
On Wed, Jan 21, 2015 at 12:52 PM, Branko Čibej wrote:
> On 21.01.2015 21:18, Dmitriy Setrakyan wrote:
> > Additionally, I wanted to find out if any one has any experience having
> > "versioned" documentation. For example, in GridGain, every time we do a
> new
> > release, we create a copy of our
On 21.01.2015 21:18, Dmitriy Setrakyan wrote:
> Additionally, I wanted to find out if any one has any experience having
> "versioned" documentation. For example, in GridGain, every time we do a new
> release, we create a copy of our documentation space for the new release
> and make changes there.
Additionally, I wanted to find out if any one has any experience having
"versioned" documentation. For example, in GridGain, every time we do a new
release, we create a copy of our documentation space for the new release
and make changes there. This way we have a separate documentation space for
ev
Hi,
Just wanted to let everyone know that I have filed INFRA ticket to do the
initial import of the GridGain Open Source documentation into Apache Ignite
space on Apache confluence wiki:
https://issues.apache.org/jira/browse/INFRA-9048
Let's hope this can be done.
D.
Semen Boikov created IGNITE-114:
---
Summary: Value is not loaded from store for invoke in
transactional cache
Key: IGNITE-114
URL: https://issues.apache.org/jira/browse/IGNITE-114
Project: Ignite
We have been assigned a new Jira workflow which has "Patch Available"
status. This allows us to submit any ticket for review by a committer and
flipping the status to "Patch Available". The committer can review the
patch and either merge it or assign back to developer.
Let's try using this process
[
https://issues.apache.org/jira/browse/IGNITE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285942#comment-14285942
]
Yakov Zhdanov commented on IGNITE-86:
-
Let's skip entire undeployment for system cache
Yakov Zhdanov created IGNITE-113:
Summary: Handle cross module javadoc links (former @gglink tag)
Key: IGNITE-113
URL: https://issues.apache.org/jira/browse/IGNITE-113
Project: Ignite
Issue T
[
https://issues.apache.org/jira/browse/IGNITE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Evdokimov resolved IGNITE-105.
-
Resolution: Fixed
> Need to add IgniteCacheConfiguration.isReadFromBackup() method
> -
[
https://issues.apache.org/jira/browse/IGNITE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285821#comment-14285821
]
Sergey Evdokimov commented on IGNITE-59:
IgniteAsyncSupport has been removed.
> S
Sergi Vladykin created IGNITE-112:
-
Summary: Move all query unit tests to new API
Key: IGNITE-112
URL: https://issues.apache.org/jira/browse/IGNITE-112
Project: Ignite
Issue Type: Test
[
https://issues.apache.org/jira/browse/IGNITE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin closed IGNITE-98.
> QA notes for job statistics
> ---
>
> Key: IGNITE-98
>
[
https://issues.apache.org/jira/browse/IGNITE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin closed IGNITE-73.
> Remove duplicate resources in distributed cache
> ---
>
>
[
https://issues.apache.org/jira/browse/IGNITE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin closed IGNITE-100.
-
> Get rid of JSON in Hadoop tests
> ---
>
> Key: IGNITE-10
[
https://issues.apache.org/jira/browse/IGNITE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin resolved IGNITE-73.
--
Resolution: Fixed
merged to sprint-1
> Remove duplicate resources in distributed cache
> ---
[
https://issues.apache.org/jira/browse/IGNITE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin resolved IGNITE-98.
--
Resolution: Fixed
merged to sprint-1
> QA notes for job statistics
> ---
[
https://issues.apache.org/jira/browse/IGNITE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin resolved IGNITE-100.
---
Resolution: Fixed
merged to sprint-1
> Get rid of JSON in Hadoop tests
>
Anton Vinogradov created IGNITE-111:
---
Summary: Check the license header of the project source files
Key: IGNITE-111
URL: https://issues.apache.org/jira/browse/IGNITE-111
Project: Ignite
Iss
[
https://issues.apache.org/jira/browse/IGNITE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Irina Vasilinets updated IGNITE-52:
---
Assignee: Alexey Goncharuk (was: Irina Vasilinets)
> Support distributed Cache.containsKey(K k
[
https://issues.apache.org/jira/browse/IGNITE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Setrakyan reassigned IGNITE-109:
Assignee: Alexey Goncharuk
> Properly use store with cross cache transactions
> --
Hi,
In the spirit of refactoring the streaming API, I want to start by renaming
IgniteDataLoader to IgniteDataStreamer? This streamer simply adds continuos
stream of keys to IgniteCache. Going forward we can add KafkaDataStreamer
which will add key-value pairs received from Kafka, etc...
Thoughts
33 matches
Mail list logo
