[jira] [Assigned] (IGNITE-4728) Web Console: Remember the screen from which user has left the previous session.
[ https://issues.apache.org/jira/browse/IGNITE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-4728: -- Assignee: Pavel Konstantinov (was: Andrey Novikov) > Web Console: Remember the screen from which user has left the previous > session. > --- > > Key: IGNITE-4728 > URL: https://issues.apache.org/jira/browse/IGNITE-4728 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Pavel Konstantinov > > Don't save latest state for demo mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4728) Web Console: Remember the screen from which user has left the previous session.
[ https://issues.apache.org/jira/browse/IGNITE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906871#comment-15906871 ] Andrey Novikov commented on IGNITE-4728: Reviewed. > Web Console: Remember the screen from which user has left the previous > session. > --- > > Key: IGNITE-4728 > URL: https://issues.apache.org/jira/browse/IGNITE-4728 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Andrey Novikov > > Don't save latest state for demo mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4587) Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode
[
https://issues.apache.org/jira/browse/IGNITE-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906659#comment-15906659
]
Maksim Kozlov commented on IGNITE-4587:
---
[~agura] yes,
http://ci.ignite.apache.org/project.html?projectId=IgniteTests_IgniteTests=pull/1521/head
Ok, I removed everything.
> Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode
> ---
>
> Key: IGNITE-4587
> URL: https://issues.apache.org/jira/browse/IGNITE-4587
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Denis Magda
>Assignee: Maksim Kozlov
> Fix For: 2.0
>
>
> {{CacheAtomicWriteOrderMode.CLOCK}} proved to be harmful in production due to
> timing issues.
> It makes sense to remove it completely in 2.0 release. Migration guide has be
> updated:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906597#comment-15906597 ] Madhawa Vidanapathirana commented on IGNITE-4600: - Hi [~dmagda], Is their any ongoing discussion already on how the Python API can be supported? (regarding 3 options given in description). If so, can you direct me to the discussion? > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Denis Magda > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906589#comment-15906589 ] Denis Magda commented on IGNITE-4600: - It depends on a number of folks who decide to work on this task. If you're the only one then the task will be fully yours. > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Denis Magda > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4797) Need to expose offheap memory allocated size metric for internal data structures
[
https://issues.apache.org/jira/browse/IGNITE-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906476#comment-15906476
]
Kartik Somani commented on IGNITE-4797:
---
[My First Bug]
The approach that I see is, I'll add the interface for getSystemAllocatedSize()
to the CacheMetrics and CacheMetricsMxBean Interface. In CacheMetricsImpl, I'll
use GridCacheContext object (cctx) object to get and return the
systemAllocatedSize using : cctx.unsafeMemory.systemAllocatedSize().
CacheLocalMetricsMxBean will then call cache.metrics0.getSystemAllocatedSize()
to return the metric.
Will this work?
> Need to expose offheap memory allocated size metric for internal data
> structures
>
>
> Key: IGNITE-4797
> URL: https://issues.apache.org/jira/browse/IGNITE-4797
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Kartik Somani
> Labels: newbie
> Fix For: 2.0
>
>
> Offheap caches expose offheap memory allocated size via
> {{CacheMetricsMXBean.getOffHeapAllocatedSize()}}. But this metric doesn't
> take into account offheap memory that allocated for internal data structures
> (GridUnsafeMap and LRU eviction policy).
> However Ignite collects this metric (see
> GridUnsafeMemory.systemAllocatedSize() method).
> Need to expose this metric via {{CacheMetricsMXBean}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906448#comment-15906448 ] Madhawa Vidanapathirana commented on IGNITE-4600: - Hi, If this ticket is to be taken forward as my GSOC Project, should it cover all 4 sub tasks? > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Denis Magda > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
