[jira] [Comment Edited] (IGNITE-1911) Discovery MessageWorker thread moves node to "zombie" state when fails
[ https://issues.apache.org/jira/browse/IGNITE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008168#comment-15008168 ] Denis Magda edited comment on IGNITE-1911 at 11/17/15 7:04 AM: --- Changes passed TC tests. Please review. was (Author: dmagda): Chan > Discovery MessageWorker thread moves node to "zombie" state when fails > -- > > Key: IGNITE-1911 > URL: https://issues.apache.org/jira/browse/IGNITE-1911 > Project: Ignite > Issue Type: Bug >Affects Versions: ignite-1.4 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Critical > Fix For: 1.5 > > Attachments: ignite-1911.patch > > > If MessageWorker thread fails by some reason (i.e. because of uncaught > exception) it will move a node to "zombie" state. The node will still accept > messages through SocketReader but won't process them. > At some point of time the node will fail because the message queue will be > overflowed. > Such a node must be stopped as soon as MessageWorker terminates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1911) Discovery MessageWorker thread moves node to "zombie" state when fails
[ https://issues.apache.org/jira/browse/IGNITE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-1911: Attachment: ignite-1911.patch Chan > Discovery MessageWorker thread moves node to "zombie" state when fails > -- > > Key: IGNITE-1911 > URL: https://issues.apache.org/jira/browse/IGNITE-1911 > Project: Ignite > Issue Type: Bug >Affects Versions: ignite-1.4 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Critical > Fix For: 1.5 > > Attachments: ignite-1911.patch > > > If MessageWorker thread fails by some reason (i.e. because of uncaught > exception) it will move a node to "zombie" state. The node will still accept > messages through SocketReader but won't process them. > At some point of time the node will fail because the message queue will be > overflowed. > Such a node must be stopped as soon as MessageWorker terminates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1929) Add code snippets for C++ and C#.
Alexey Kuznetsov created IGNITE-1929: Summary: Add code snippets for C++ and C#. Key: IGNITE-1929 URL: https://issues.apache.org/jira/browse/IGNITE-1929 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.5 Reporter: Alexey Kuznetsov Priority: Minor Fix For: 1.5 We need to generate code for C++ and C# the same way we do for Java. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1762) Chart settings should be preserved between charts type switch
[ https://issues.apache.org/jira/browse/IGNITE-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-1762: - Summary: Chart settings should be preserved between charts type switch (was: Chart settings should be preserved between chats type switch) > Chart settings should be preserved between charts type switch > - > > Key: IGNITE-1762 > URL: https://issues.apache.org/jira/browse/IGNITE-1762 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Alexey Kuznetsov > Fix For: 1.5 > > > In current implementation we simply recreate char every time we change chart > type (for example: bar chart -> pie chart), but for better user experience it > will be better to memorize current settings and restore them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1926) Implement IgfsSecondaryFileSystem using java.io.File API
[ https://issues.apache.org/jira/browse/IGNITE-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1926: Component/s: newbie > Implement IgfsSecondaryFileSystem using java.io.File API > > > Key: IGNITE-1926 > URL: https://issues.apache.org/jira/browse/IGNITE-1926 > Project: Ignite > Issue Type: Improvement > Components: IGFS, newbie >Reporter: Valentin Kulichenko > Labels: newbie > > This will allow to persist IGFS data on the local disk. Currently we have > only Hadoop-based implementation. > Corresponding user thread: > http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-td1882.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1762) Chart settings should be preserved between chats type switch
[ https://issues.apache.org/jira/browse/IGNITE-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1762. -- Assignee: (was: Pavel Konstantinov) Tested. > Chart settings should be preserved between chats type switch > > > Key: IGNITE-1762 > URL: https://issues.apache.org/jira/browse/IGNITE-1762 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Alexey Kuznetsov > Fix For: 1.5 > > > In current implementation we simply recreate char every time we change chart > type (for example: bar chart -> pie chart), but for better user experience it > will be better to memorize current settings and restore them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1867) Fix java class names and package declaration
[ https://issues.apache.org/jira/browse/IGNITE-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko resolved IGNITE-1867. --- Resolution: Fixed Assignee: Pavel Konstantinov (was: Vasiliy Sisko) # Fixed c3p0 datasource. # Added client near cache configuration on client snippet presentation. > Fix java class names and package declaration > > > Key: IGNITE-1867 > URL: https://issues.apache.org/jira/browse/IGNITE-1867 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Prachi Garg >Assignee: Pavel Konstantinov > Fix For: 1.5 > > > I noticed a few issues when I imported my project, created using the web > console, in IDEA - > 1. ServerConfigurationFactory class name is create in the file called > “ConfigurationFactory.java”. Class name and file name should be the same. > 2. The package declaration for ClientConfigurationFactory and > SeverConfigurationFactory classes is missing. > 3. There should be simple 'nodeStartup' class for starting a node, in the > IDE, using the XML configuration file. > 4. Missing near configuration for client in java code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1928) Area chart shows incorrect graph on first page in special case
[
https://issues.apache.org/jira/browse/IGNITE-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1928:
---
Summary: Area chart shows incorrect graph on first page in special case
(was: Area chart shows incorrect graf on first page in special case)
> Area chart shows incorrect graph on first page in special case
> --
>
> Key: IGNITE-1928
> URL: https://issues.apache.org/jira/browse/IGNITE-1928
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
> Attachments: ig-1928.png
>
>
> I'm tested area chart with this query
> {code}
> select _key, _val, random() from car
> {code}
> Please see the result in attachment
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1928) Area chart shows incorrect graf on first page in special case
[
https://issues.apache.org/jira/browse/IGNITE-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1928:
---
Attachment: ig-1928.png
> Area chart shows incorrect graf on first page in special case
> -
>
> Key: IGNITE-1928
> URL: https://issues.apache.org/jira/browse/IGNITE-1928
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
> Attachments: ig-1928.png
>
>
> I'm tested area chart with this query
> {code}
> select _key, _val, random() from car
> {code}
> Please see the result in attachment
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1928) Area chart shows incorrect graf on first page in special case
Pavel Konstantinov created IGNITE-1928:
--
Summary: Area chart shows incorrect graf on first page in special
case
Key: IGNITE-1928
URL: https://issues.apache.org/jira/browse/IGNITE-1928
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
Priority: Minor
Attachments: ig-1928.png
I'm tested area chart with this query
{code}
select _key, _val, random() from car
{code}
Please see the result in attachment
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1927) Show generated pom file on summary page
Vasiliy Sisko created IGNITE-1927: - Summary: Show generated pom file on summary page Key: IGNITE-1927 URL: https://issues.apache.org/jira/browse/IGNITE-1927 Project: Ignite Issue Type: Sub-task Affects Versions: 1.5 Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Priority: Minor Fix For: 1.5 Show pom file as option of chosen presentation on Java tab. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1920) Chart should select as y axis value different from x axis value if it is possible.
[ https://issues.apache.org/jira/browse/IGNITE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1920. -- Assignee: (was: Pavel Konstantinov) Tested. > Chart should select as y axis value different from x axis value if it is > possible. > -- > > Key: IGNITE-1920 > URL: https://issues.apache.org/jira/browse/IGNITE-1920 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Vasiliy Sisko >Priority: Minor > Fix For: 1.5 > > > Execute query where exist two number column. Chart select first column for x > and y axis to show. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1926) Implement IgfsSecondaryFileSystem using java.io.File API
[ https://issues.apache.org/jira/browse/IGNITE-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1926: Labels: newbie (was: ) > Implement IgfsSecondaryFileSystem using java.io.File API > > > Key: IGNITE-1926 > URL: https://issues.apache.org/jira/browse/IGNITE-1926 > Project: Ignite > Issue Type: Improvement > Components: IGFS >Reporter: Valentin Kulichenko > Labels: newbie > > This will allow to persist IGFS data on the local disk. Currently we have > only Hadoop-based implementation. > Corresponding user thread: > http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-td1882.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1926) Implement IgfsSecondaryFileSystem using java.io.File API
Valentin Kulichenko created IGNITE-1926: --- Summary: Implement IgfsSecondaryFileSystem using java.io.File API Key: IGNITE-1926 URL: https://issues.apache.org/jira/browse/IGNITE-1926 Project: Ignite Issue Type: Improvement Components: IGFS Reporter: Valentin Kulichenko This will allow to persist IGFS data on the local disk. Currently we have only Hadoop-based implementation. Corresponding user thread: http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-td1882.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume
[
https://issues.apache.org/jira/browse/IGNITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007555#comment-15007555
]
Roman Shtykh commented on IGNITE-529:
-
Anton,
v1.5 is not visible to me. I might need some permissions.
> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from
> Apache Flume and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1903) CacheStore implementation is serialised to grid clients whether they require it or not
[
https://issues.apache.org/jira/browse/IGNITE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Setrakyan updated IGNITE-1903:
--
Description:
See User discussion thread:
http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
Brief summary: When a grid client joins the grid (clientMode=true) it receives
a message from the server node(s) on the grid that contains the serialized
CacheStore implementation object. If the client does not have this class on
its CLASSPATH (and there is no reason it should, as it is a client) then the
de-serialization of this message will fail, causing this exception:
{code}SEVERE: Failed to unmarshal discovery data for component: 1
class org.apache.ignite.IgniteCheckedException: Failed to find class with given
class loader for unmarshalling (make sure same versions of all classes are
available on all nodes or enable peer-class-loading):
sun.misc.Launcher$AppClassLoader@14dad5dc
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:104)
at
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:67)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1529)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1317)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1229)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1199)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.lang.ClassNotFoundException:
c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite
{code}
where {{c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}} is the CacheStore
implementation.
The ostensible reason for the CacheStore serialization is so that clients of a
TRANSACTIONAL cache can begin the transaction on the underlying store.
The only current solution to this is to add the grid node's CacheStore
implementation class definition to the CLASSPATH of the client. This creates
an *undesirable coupling* between server and client.
was:
See User discussion thread:
http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
Brief summary: When a grid client joins the grid (clientMode=true) it receives
a message from the server node(s) on the grid that contains the serialized
CacheStore implementation object. If the client does not have this class on
its CLASSPATH (and there is no reason it should, as it is a client) then the
de-serialization of this message will fail, causing this exception:
{code}SEVERE: Failed to unmarshal discovery data for component: 1
class org.apache.ignite.IgniteCheckedException: Failed to find class with given
class loader for unmarshalling (make sure same versions of all classes are
available on all nodes or enable peer-class-loading):
sun.misc.Launcher$AppClassLoader@14dad5dc
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:104)
at
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:67)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1529)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1317)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1229)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1199)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.lang.ClassNotFoundException:
c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}}
{code}
where {{c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}} is the CacheStore
implementation.
The ostensible reason for the CacheStore serialization is so that clients of a
TRANSACTIONAL cache can begin the transaction on the underlying store.
The only current solution to this is to add the grid node's CacheStore
implementation class definition to the CLASSPATH of the client. This creates
an *undesirable coupling* between server and client.
> CacheStore implementation is serialised to grid clients whether they require
> it or not
> --
>
> Key: IGNITE-1903
> URL: https://issues.apache.org/jira/browse/IGNITE-1903
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Michael Griggs
> Fix For: 1.6
>
>
> See User discussion thread:
> http://apache-ignite-users.70518.x6.nabble.com/Cache
[jira] [Updated] (IGNITE-1903) CacheStore implementation is serialised to grid clients whether they require it or not
[
https://issues.apache.org/jira/browse/IGNITE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Setrakyan updated IGNITE-1903:
--
Description:
See User discussion thread:
http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
Brief summary: When a grid client joins the grid (clientMode=true) it receives
a message from the server node(s) on the grid that contains the serialized
CacheStore implementation object. If the client does not have this class on
its CLASSPATH (and there is no reason it should, as it is a client) then the
de-serialization of this message will fail, causing this exception:
{code}SEVERE: Failed to unmarshal discovery data for component: 1
class org.apache.ignite.IgniteCheckedException: Failed to find class with given
class loader for unmarshalling (make sure same versions of all classes are
available on all nodes or enable peer-class-loading):
sun.misc.Launcher$AppClassLoader@14dad5dc
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:104)
at
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:67)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1529)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1317)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1229)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1199)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.lang.ClassNotFoundException:
c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}}
{code}
where {{c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}} is the CacheStore
implementation.
The ostensible reason for the CacheStore serialization is so that clients of a
TRANSACTIONAL cache can begin the transaction on the underlying store.
The only current solution to this is to add the grid node's CacheStore
implementation class definition to the CLASSPATH of the client. This creates
an *undesirable coupling* between server and client.
was:
See User discussion thread:
http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
Brief summary: When a grid client joins the grid (clientMode=true) it receives
a message from the server node(s) on the grid that contains the serialized
CacheStore implementation object. If the client does not have this class on
its CLASSPATH (and there is no reason it should, as it is a client) then the
de-serialization of this message will fail, causing this exception:
{{SEVERE: Failed to unmarshal discovery data for component: 1
class org.apache.ignite.IgniteCheckedException: Failed to find class with given
class loader for unmarshalling (make sure same versions of all classes are
available on all nodes or enable peer-class-loading):
sun.misc.Launcher$AppClassLoader@14dad5dc
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:104)
at
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:67)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1529)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1317)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1229)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1199)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.lang.ClassNotFoundException:
c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}}
where {{c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}} is the CacheStore
implementation.
The ostensible reason for the CacheStore serialization is so that clients of a
TRANSACTIONAL cache can begin the transaction on the underlying store.
The only current solution to this is to add the grid node's CacheStore
implementation class definition to the CLASSPATH of the client. This creates
an *undesirable coupling* between server and client.
> CacheStore implementation is serialised to grid clients whether they require
> it or not
> --
>
> Key: IGNITE-1903
> URL: https://issues.apache.org/jira/browse/IGNITE-1903
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Michael Griggs
> Fix For: 1.6
>
>
> See User discussion thread:
> http://apache-ignite-users.70518.x6.nabble.com/CacheStore-be
[jira] [Comment Edited] (IGNITE-1923) [Test failed] IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed fails with portable marshaller
[
https://issues.apache.org/jira/browse/IGNITE-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006873#comment-15006873
]
Andrey Gura edited comment on IGNITE-1923 at 11/16/15 4:27 PM:
---
This test affects {{testResponseMessageOnUnmarshallingFailed}}. Actually any
additional {{put}} into cache lead to H2 indexing related exception. This
problem fixed in ingite-1282 branch.
For now I just changed {{testResponseMessageOnRequestUnmarshallingFailed}} test
in order to don't affect {{testResponseMessageOnUnmarshallingFailed}} test.
TC looks good. Please review.
was (Author: agura):
This test affects {{testResponseMessageOnUnmarshallingFailed}}. Actually any
additional {{put}} into cache lead to H2 indexing related exception. This
problem fixed in ingite-1282 branch.
For now I just change {{testResponseMessageOnRequestUnmarshallingFailed}} test
in order to don't affect {{testResponseMessageOnUnmarshallingFailed}} test.
TC looks good. Please review.
> [Test failed]
> IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed
> fails with portable marshaller
> --
>
> Key: IGNITE-1923
> URL: https://issues.apache.org/jira/browse/IGNITE-1923
> Project: Ignite
> Issue Type: Test
>Reporter: Andrey Gura
>Priority: Trivial
> Fix For: 1.5
>
>
> {{IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed}}
> fails with portable marshaller. Test is incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1920) Chart should select as y axis value different from x axis value if it is possible.
[ https://issues.apache.org/jira/browse/IGNITE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1920. -- Resolution: Fixed Assignee: Pavel Konstantinov (was: Vasiliy Sisko) Fixed chart column selection logic. Please test with one, two, three numeric and not numeric columns. > Chart should select as y axis value different from x axis value if it is > possible. > -- > > Key: IGNITE-1920 > URL: https://issues.apache.org/jira/browse/IGNITE-1920 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 1.5 > > > Execute query where exist two number column. Chart select first column for x > and y axis to show. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume
[
https://issues.apache.org/jira/browse/IGNITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006747#comment-15006747
]
Anton Vinogradov commented on IGNITE-529:
-
Roman,
do you have access to
https://apacheignite.readme.io/v1.5/docs/flume-data-streamer ? (You have to
register yourself at readme.io first)
> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from
> Apache Flume and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1917) Portables: micro optimizations.
[ https://issues.apache.org/jira/browse/IGNITE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006730#comment-15006730 ] Vladimir Ozerov commented on IGNITE-1917: - Further work on write performance. Major changes are: 1) Removed schema hash re-calc for Serializable types. 2) Removed boundaries checks where possible. 3) Optimized handles management in the most common case - when there are no nested objects. Results are very good: Case A: Serializable object with 40 int fields Optimized:2,1 M/sec Portable, before: 0,8 M/sec Portable, after: 2,3 M/sec Case B: Externalizable/Binarizable object with 4 fields, two ints and two strings Optimized:2,9 M/sec Portable, before: 2,6 M/sec Portable, after: 3,1 M/sec In both cases we outperform OptimizedMarshaller. Even though in case A it produces 167 bytes vs 264 for PortableMarshaller. Honestly, I haven't expected we will be able to outperform OptimizedMarshaller. The most critical gain was form removed boundaries checks. Probably the same technique could be applied to other marshalling logic, especially "direct marshallable". > Portables: micro optimizations. > --- > > Key: IGNITE-1917 > URL: https://issues.apache.org/jira/browse/IGNITE-1917 > Project: Ignite > Issue Type: Task > Components: general, interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1925) Test HadoopSkipListSelfTest.testLevel flakily fails
[ https://issues.apache.org/jira/browse/IGNITE-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky updated IGNITE-1925: Description: Test HadoopSkipListSelfTest.testLevel fails from time to time with ~ 3% probability. junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:55) at junit.framework.Assert.assertTrue(Assert.java:22) at junit.framework.Assert.assertTrue(Assert.java:31) at junit.framework.TestCase.assertTrue(TestCase.java:201) at org.apache.ignite.internal.processors.hadoop.shuffle.collections.HadoopSkipListSelfTest.testLevel(HadoopSkipListSelfTest.java:83) was: Test HadoopSkipListSelfTest.testLevel fails from time to time with ~ 3% probability. junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:55) at junit.framework.Assert.assertTrue(Assert.java:22) at junit.framework.Assert.assertTrue(Assert.java:31) at junit.framework.TestCase.assertTrue(TestCase.java:201) at org.apache.ignite.internal.processors.hadoop.shuffle.collections.HadoopSkipListSelfTest.testLevel(HadoopSkipListSelfTest.java:83) --- Stdout: --- > Test HadoopSkipListSelfTest.testLevel flakily fails > --- > > Key: IGNITE-1925 > URL: https://issues.apache.org/jira/browse/IGNITE-1925 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky >Priority: Minor > > Test HadoopSkipListSelfTest.testLevel fails from time to time with ~ 3% > probability. > > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at > org.apache.ignite.internal.processors.hadoop.shuffle.collections.HadoopSkipListSelfTest.testLevel(HadoopSkipListSelfTest.java:83) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1925) Test HadoopSkipListSelfTest.testLevel flakily fails
Ivan Veselovsky created IGNITE-1925: --- Summary: Test HadoopSkipListSelfTest.testLevel flakily fails Key: IGNITE-1925 URL: https://issues.apache.org/jira/browse/IGNITE-1925 Project: Ignite Issue Type: Bug Reporter: Ivan Veselovsky Assignee: Ivan Veselovsky Priority: Minor Test HadoopSkipListSelfTest.testLevel fails from time to time with ~ 3% probability. junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:55) at junit.framework.Assert.assertTrue(Assert.java:22) at junit.framework.Assert.assertTrue(Assert.java:31) at junit.framework.TestCase.assertTrue(TestCase.java:201) at org.apache.ignite.internal.processors.hadoop.shuffle.collections.HadoopSkipListSelfTest.testLevel(HadoopSkipListSelfTest.java:83) --- Stdout: --- -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1227) Need to implement Ignite-based Spring transaction manager
[
https://issues.apache.org/jira/browse/IGNITE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006686#comment-15006686
]
ASF GitHub Bot commented on IGNITE-1227:
GitHub user amirakhmedov opened a pull request:
https://github.com/apache/ignite/pull/239
IGNITE-1227: spring transaction manager implementation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/amirakhmedov/ignite ignite-1227
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/239.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #239
commit aa2b51a17a13695e4d1114c25cd8e76e620ae851
Author: Amir Akhmedov
Date: 2015-11-13T22:04:41Z
IGNITE-1227: spring transaction manager implementation
> Need to implement Ignite-based Spring transaction manager
> -
>
> Key: IGNITE-1227
> URL: https://issues.apache.org/jira/browse/IGNITE-1227
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Labels: newbie
> Attachments: IGNITE-1227.patch
>
>
> This will allow to use Spring transaction interceptor for wrapping cache
> operations into Ignite transaction.
> Essentially, we need to implement Spring's {{PlatformTransactionManager}}
> interface using {{IgniteTransactions}} API.
> Corresponding user list thread:
> http://apache-ignite-users.70518.x6.nabble.com/Transactions-td885.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume
[
https://issues.apache.org/jira/browse/IGNITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006679#comment-15006679
]
Roman Shtykh commented on IGNITE-529:
-
Anton, PR is updated.
Please let me know when you create a page. I'll write the text.
> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from
> Apache Flume and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1924) Incomplete marshaller cache rebalancing causes Grid hangs
[ https://issues.apache.org/jira/browse/IGNITE-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1924: Summary: Incomplete marshaller cache rebalancing causes Grid hangs (was: Uncompleme marshaller cashe rebalancing cause Grid hangs) > Incomplete marshaller cache rebalancing causes Grid hangs > - > > Key: IGNITE-1924 > URL: https://issues.apache.org/jira/browse/IGNITE-1924 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Critical > > End of the log. > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,947][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=20660c29-91a1-4279-9dc1-88d192bc6002, partitionsCount=6, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220587%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220586%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > Hang on: > [11:51:56] : [org.apache.ignite:ignite-core] Thread > [name="ignite-#220562%sys-tcp.IgniteCacheSslStartStopSelfTest3%", id=287517, > state=WAITING, blockCnt=0, waitCnt=3] > [11:51:56] : [org.apache.ignite:ignite-core] Lock > [object=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture@b402f89, > ownerName=null, ownerId=-1] > [11:51:56] : [org.apache.ignite:ignite-core] at > sun.misc.Unsafe.park(Native Method) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.waitForCacheRebalancing(GridDhtPartitionDemander.java:265) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.access$400(GridDhtPartitionDemander.java:85) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:323) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:320) > [11:51:56] : [org.apache.ignite:i
[jira] [Created] (IGNITE-1924) Uncompleme marshaller cashe rebalancing cause Grid hangs
Anton Vinogradov created IGNITE-1924: Summary: Uncompleme marshaller cashe rebalancing cause Grid hangs Key: IGNITE-1924 URL: https://issues.apache.org/jira/browse/IGNITE-1924 Project: Ignite Issue Type: Bug Reporter: Anton Vinogradov Assignee: Anton Vinogradov Priority: Critical End of the log. [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,947][INFO ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] Starting rebalancing [cache=ignite-marshaller-sys-cache, mode=SYNC, fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, partitionsCount=7, topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] Starting rebalancing [cache=ignite-marshaller-sys-cache, mode=SYNC, fromNode=20660c29-91a1-4279-9dc1-88d192bc6002, partitionsCount=6, topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] Starting rebalancing [cache=ignite-marshaller-sys-cache, mode=SYNC, fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, partitionsCount=7, topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO ][ignite-#220587%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] Completed rebalancing [cache=ignite-marshaller-sys-cache, fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO ][ignite-#220586%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] Completed rebalancing [cache=ignite-marshaller-sys-cache, fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] Hang on: [11:51:56] : [org.apache.ignite:ignite-core] Thread [name="ignite-#220562%sys-tcp.IgniteCacheSslStartStopSelfTest3%", id=287517, state=WAITING, blockCnt=0, waitCnt=3] [11:51:56] : [org.apache.ignite:ignite-core] Lock [object=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture@b402f89, ownerName=null, ownerId=-1] [11:51:56] : [org.apache.ignite:ignite-core] at sun.misc.Unsafe.park(Native Method) [11:51:56] : [org.apache.ignite:ignite-core] at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) [11:51:56] : [org.apache.ignite:ignite-core] at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) [11:51:56] : [org.apache.ignite:ignite-core] at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) [11:51:56] : [org.apache.ignite:ignite-core] at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) [11:51:56] : [org.apache.ignite:ignite-core] at o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157) [11:51:56] : [org.apache.ignite:ignite-core] at o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115) [11:51:56] : [org.apache.ignite:ignite-core] at o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.waitForCacheRebalancing(GridDhtPartitionDemander.java:265) [11:51:56] : [org.apache.ignite:ignite-core] at o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.access$400(GridDhtPartitionDemander.java:85) [11:51:56] : [org.apache.ignite:ignite-core] at o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:323) [11:51:56] : [org.apache.ignite:ignite-core] at o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:320) [11:51:56] : [org.apache.ignite:ignite-core] at o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker$1.call(GridCachePartitionExchangeManager.java:1386) [11:51:56] : [org.apache.ignite:ignite-core] at o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker$1.call(GridCachePartitionExchangeManager.java:1377) [11:51:56] : [org.apache.ignite:ign
[jira] [Commented] (IGNITE-1923) [Test failed] IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed fails with portable marshaller
[
https://issues.apache.org/jira/browse/IGNITE-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006639#comment-15006639
]
Andrey Gura commented on IGNITE-1923:
-
In order to unmarshalling error happen {{readObject}} method of scan query
filter throws {{IOException}}. It is ok for {{JdkMarshaller}}. But
{{PortableMarshaller}} will use {{readObject}} and {{writeObject}} methods only
if both of them are defined in class.
Fixed in PR https://github.com/apache/ignite/pull/238
Waiting for TC.
> [Test failed]
> IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed
> fails with portable marshaller
> --
>
> Key: IGNITE-1923
> URL: https://issues.apache.org/jira/browse/IGNITE-1923
> Project: Ignite
> Issue Type: Test
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Trivial
> Fix For: 1.5
>
>
> {{IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed}}
> fails with portable marshaller. Test is incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1907) .Net: Cache configuration
[ https://issues.apache.org/jira/browse/IGNITE-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-1907: --- Assignee: Pavel Tupitsyn > .Net: Cache configuration > - > > Key: IGNITE-1907 > URL: https://issues.apache.org/jira/browse/IGNITE-1907 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: 1.5 > > > Configure cache in code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1894) .Net: Delegate support in the API via extension methods
[ https://issues.apache.org/jira/browse/IGNITE-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006603#comment-15006603 ] ASF GitHub Bot commented on IGNITE-1894: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/237 IGNITE-1894 .Net: Delegate support in the API via extension methods You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1894 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/237.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #237 commit e167b30ca643ca57cfcc1bab2ff31b35ab2ce120 Author: Pavel Tupitsyn Date: 2015-11-13T12:52:05Z IGNITE-1910 .Net: Possible handle leak in ScanQuery commit fab5c723dc9d8926ed88f52af9d047de63afa31f Author: Pavel Tupitsyn Date: 2015-11-13T13:26:52Z Fix predicate close in Java commit 745907c43f1a1572f48db7b1543a0e7ac1218503 Author: Pavel Tupitsyn Date: 2015-11-13T13:46:03Z IGNITE-1894 .Net: Delegate support in the API via extension methods commit 1fe07ce6938e3c827e77e4e38d0920b2ce6f1f35 Author: Pavel Tupitsyn Date: 2015-11-13T13:47:55Z wip commit 7cb1ac7a405b8c392713eb9677f240ccfc0592cf Author: Pavel Tupitsyn Date: 2015-11-13T13:51:10Z Cache test commit ce02e7a82cb46e9b982c0611a974a75429b8bdb1 Author: Pavel Tupitsyn Date: 2015-11-13T13:53:35Z Fix naming commit 1eeea6efaae36a63ec14dec746ad1390904e78bf Author: Pavel Tupitsyn Date: 2015-11-13T13:55:13Z Merge branch 'ignite-1910' into ignite-1894 commit 12855ae61c25ec8972af155970120d330ed04bbb Author: Pavel Tupitsyn Date: 2015-11-13T14:10:17Z Fix similar issue in CacheStore commit 75f1315f869415e2e852e3a1f7514441ff44e572 Author: Pavel Tupitsyn Date: 2015-11-13T14:13:42Z Merge branch 'ignite-1910' into ignite-1894 commit ccfc3eabb730239eed2c5973fd6a271623f0c683 Author: Pavel Tupitsyn Date: 2015-11-13T14:40:33Z Failing test added commit 4ce90965153dcdba40cf59d394cd8e7ffec25d7b Author: Pavel Tupitsyn Date: 2015-11-13T14:44:42Z wip commit 54e41fb452d1eedb52aeb6c1cfb03017a4dcb4b8 Author: Pavel Tupitsyn Date: 2015-11-13T15:12:04Z wip commit 51a72ecc6a530dcee0e7b198f8ff6c7bbde48101 Author: Pavel Tupitsyn Date: 2015-11-13T15:12:58Z wip commit 54f2f9aeb6a67d8332dfbccbd5c63c34ae3368b4 Author: Pavel Tupitsyn Date: 2015-11-13T15:17:19Z wip commit 225ca15089d81a29bd5281b8634f5c29674b114c Author: Pavel Tupitsyn Date: 2015-11-13T15:35:49Z wip commit 9eb949908ad989e8d40d41be15274ce04c53ca0b Author: Pavel Tupitsyn Date: 2015-11-13T15:49:29Z Fix test commit b18710311ea5ea9b1b19a0214ae746da9f501d4d Author: Pavel Tupitsyn Date: 2015-11-13T16:06:53Z Get rid of boxing commit 7f8d2f1574b3bd8b5a76e141c85eb6e603abbd09 Author: Pavel Tupitsyn Date: 2015-11-16T09:37:35Z Merge ContinuousQuery fix (IGNITE-1912) commit ed81d5afbf63b0841e47aafec4974c3996be7f22 Author: Pavel Tupitsyn Date: 2015-11-16T09:54:00Z wip ruleset commit 2cca96852f77e1e25d1b215a0c04f375b0048e41 Author: Pavel Tupitsyn Date: 2015-11-16T10:01:25Z ComputeExtensions added commit 1445e974ca29bf1631107a45b9847ce6c87a29b5 Author: Pavel Tupitsyn Date: 2015-11-16T10:05:14Z Fixing tests commit d277388dfe94c302f25034c8319d9c240a817088 Author: Pavel Tupitsyn Date: 2015-11-16T10:09:50Z Fix naming commit 31e001010ee4352ef5913fd3c1619789a599d358 Author: Pavel Tupitsyn Date: 2015-11-16T10:17:38Z IGNITE-1921 .Net: Handle leak during ComputeJobHolder serialization commit 989d2d9e617d4e0f1aa5dc59feddb8001ea64513 Author: Pavel Tupitsyn Date: 2015-11-16T10:28:27Z Fix ComputeTaskHolder commit 89a068b37c026c3045e6e9bd4670ff96ef242a22 Author: Pavel Tupitsyn Date: 2015-11-16T10:40:44Z Add tests commit 50ca9bf3a9a4cccd20a9911068eb36b8a680d002 Author: Pavel Tupitsyn Date: 2015-11-16T10:42:31Z wip commit 0c43d1def75c2548d8e262436cc0ca231b4f3714 Author: Pavel Tupitsyn Date: 2015-11-16T10:46:07Z Merge ignite-1921 leak fix commit 11db2760d0cfff21a29ee4d3628331f7b817d5e5 Author: Pavel Tupitsyn Date: 2015-11-16T11:00:08Z Events extensions commit 8cdf0d593f63423c68d3ce5b702a1d26556b554b Author: Pavel Tupitsyn Date: 2015-11-16T11:07:26Z Events extensions test commit 84a43e6da9ca617dce5a87ebb8630d7131d420e4 Author: Pavel Tupitsyn Date: 2015-11-16T11:09:47Z MessagingExtensions > .Net: Delegate support in the API via extension methods > --- > > Key: IGNITE-1894 > URL: https://issues.apache.org/jira/browse/IGNITE-1894 > Project: Ignite > Issue Type: Improvemen
[jira] [Updated] (IGNITE-1903) CacheStore implementation is serialised to grid clients whether they require it or not
[
https://issues.apache.org/jira/browse/IGNITE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1903:
Fix Version/s: 1.6
> CacheStore implementation is serialised to grid clients whether they require
> it or not
> --
>
> Key: IGNITE-1903
> URL: https://issues.apache.org/jira/browse/IGNITE-1903
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Michael Griggs
> Fix For: 1.6
>
>
> See User discussion thread:
> http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
> Brief summary: When a grid client joins the grid (clientMode=true) it
> receives a message from the server node(s) on the grid that contains the
> serialized CacheStore implementation object. If the client does not have
> this class on its CLASSPATH (and there is no reason it should, as it is a
> client) then the de-serialization of this message will fail, causing this
> exception:
> {{SEVERE: Failed to unmarshal discovery data for component: 1
> class org.apache.ignite.IgniteCheckedException: Failed to find class with
> given class loader for unmarshalling (make sure same versions of all classes
> are available on all nodes or enable peer-class-loading):
> sun.misc.Launcher$AppClassLoader@14dad5dc
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:104)
>
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:67)
>
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1529)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1317)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1229)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1199)
>
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.lang.ClassNotFoundException:
> c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}}
> where {{c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}} is the CacheStore
> implementation.
> The ostensible reason for the CacheStore serialization is so that clients of
> a TRANSACTIONAL cache can begin the transaction on the underlying store.
> The only current solution to this is to add the grid node's CacheStore
> implementation class definition to the CLASSPATH of the client. This creates
> an *undesirable coupling* between server and client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1923) [Test failed] IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed fails with portable marshaller
Andrey Gura created IGNITE-1923:
---
Summary: [Test failed]
IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed
fails with portable marshaller
Key: IGNITE-1923
URL: https://issues.apache.org/jira/browse/IGNITE-1923
Project: Ignite
Issue Type: Test
Reporter: Andrey Gura
Assignee: Andrey Gura
Priority: Trivial
Fix For: 1.5
{{IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed}}
fails with portable marshaller. Test is incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1922) Add auth support to YARN module
Nikolay Tikhonov created IGNITE-1922: Summary: Add auth support to YARN module Key: IGNITE-1922 URL: https://issues.apache.org/jira/browse/IGNITE-1922 Project: Ignite Issue Type: Improvement Affects Versions: ignite-1.4 Reporter: Nikolay Tikhonov Fix For: 1.6 User list discussion: http://apache-ignite-users.70518.x6.nabble.com/Exception-in-Kerberos-Yarn-cluster-td1950.html#a1965 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume
[
https://issues.apache.org/jira/browse/IGNITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006543#comment-15006543
]
Anton Vinogradov edited comment on IGNITE-529 at 11/16/15 11:24 AM:
Roman,
- I'll create page at readme.io,
- You'll propose page's fix (using editor),
- I'll check and accept it.
Format should be simillar to other documentation.
was (Author: avinogradov):
Roman,
- I'll created page at readme.io,
- You'll propose page's fix (using editor),
- I'll check and accept it.
Format should be simillar to other documentation.
> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from
> Apache Flume and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume
[
https://issues.apache.org/jira/browse/IGNITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006543#comment-15006543
]
Anton Vinogradov commented on IGNITE-529:
-
Roman,
- I'll created page at readme.io,
- You'll propose page's fix (using editor),
- I'll check and accept it.
Format should be simillar to other documentation.
> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from
> Apache Flume and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume
[
https://issues.apache.org/jira/browse/IGNITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006533#comment-15006533
]
Roman Shtykh commented on IGNITE-529:
-
Anton, thanks a lot for improvements! I'll merge them tonight and update PR.
I'll prepare a description based on README. Can I edit directly on the Web
site? What is the normal procedure? If not, what should be the format of the
document?
> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from
> Apache Flume and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1921) .Net: Handle leak during ComputeJobHolder serialization
[ https://issues.apache.org/jira/browse/IGNITE-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006488#comment-15006488 ] ASF GitHub Bot commented on IGNITE-1921: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/236 IGNITE-1921 .Net: Handle leak during ComputeJobHolder serialization You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1921 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/236.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #236 commit 31e001010ee4352ef5913fd3c1619789a599d358 Author: Pavel Tupitsyn Date: 2015-11-16T10:17:38Z IGNITE-1921 .Net: Handle leak during ComputeJobHolder serialization commit 989d2d9e617d4e0f1aa5dc59feddb8001ea64513 Author: Pavel Tupitsyn Date: 2015-11-16T10:28:27Z Fix ComputeTaskHolder commit 89a068b37c026c3045e6e9bd4670ff96ef242a22 Author: Pavel Tupitsyn Date: 2015-11-16T10:40:44Z Add tests > .Net: Handle leak during ComputeJobHolder serialization > --- > > Key: IGNITE-1921 > URL: https://issues.apache.org/jira/browse/IGNITE-1921 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Blocker > Fix For: 1.5 > > > See where ComputeJobHolder is constructed and serialized. In case of > non-serializable user job there is a handle leak. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1200) Add IGFS configuration support
[ https://issues.apache.org/jira/browse/IGNITE-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1200. -- Assignee: (was: Pavel Konstantinov) Tested. > Add IGFS configuration support > -- > > Key: IGNITE-1200 > URL: https://issues.apache.org/jira/browse/IGNITE-1200 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: ignite-1.4 >Reporter: Alexey Kuznetsov > Fix For: 1.5 > > > We need to support IGFS configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1921) .Net: Handle leak during ComputeJobHolder serialization
Pavel Tupitsyn created IGNITE-1921: --- Summary: .Net: Handle leak during ComputeJobHolder serialization Key: IGNITE-1921 URL: https://issues.apache.org/jira/browse/IGNITE-1921 Project: Ignite Issue Type: Bug Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Priority: Blocker Fix For: 1.5 See where ComputeJobHolder is constructed and serialized. In case of non-serializable user job there is a handle leak. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1920) Chart should select as y axis value different from x axis value if it is possible.
Vasiliy Sisko created IGNITE-1920: - Summary: Chart should select as y axis value different from x axis value if it is possible. Key: IGNITE-1920 URL: https://issues.apache.org/jira/browse/IGNITE-1920 Project: Ignite Issue Type: Sub-task Affects Versions: 1.5 Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Priority: Minor Fix For: 1.5 Execute query where exist two number column. Chart select first column for x and y axis to show. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1870) Add aggregation function for Y axes values in TIME_LINE mode
[ https://issues.apache.org/jira/browse/IGNITE-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1870. -- Assignee: (was: Pavel Konstantinov) Tested. > Add aggregation function for Y axes values in TIME_LINE mode > > > Key: IGNITE-1870 > URL: https://issues.apache.org/jira/browse/IGNITE-1870 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Alexey Kuznetsov > Fix For: 1.5 > > > Add support for: First, Last, Min, Max, Avg, Sum, Count -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume
[
https://issues.apache.org/jira/browse/IGNITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006401#comment-15006401
]
Anton Vinogradov commented on IGNITE-529:
-
Roman,
I've reduced test duration from minute to 8 seconds (reconfigured settings.xml
IpFinder) & added ignite-log4j fo fix errors at test's output.
Also I've made couple of minor changes ;)
https://github.com/avinogradovgg/ignite/commit/ff517041dc18b75ba652d96e1531ffc0a68b725b
Code seems to be ready to be committed in case you agree with my changes.
Also, we have to describe usage of IgniteSink at
https://apacheignite.readme.io/v1.5/docs.
Could you please prepare article text?
> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from
> Apache Flume and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1626) .Net: Create NuGet package.
[ https://issues.apache.org/jira/browse/IGNITE-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-1626: --- Assignee: Vladimir Ozerov (was: Pavel Tupitsyn) > .Net: Create NuGet package. > --- > > Key: IGNITE-1626 > URL: https://issues.apache.org/jira/browse/IGNITE-1626 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.5 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > > *Overview* > To boost usage of the product we need to distribute it using NuGet, which is > tightly integrated with Visual Studio. > To achieve this several technical, infrastructure and marketing tasks must be > completed. > *Technical tasks* > - Apache Ignite.NET heavily depends on relative positions of compiled Java > classes. We must be able to apply different classpath search strategies > depending on packaging. This includes normal search in exploded build > directory, search in NuGet package, search in local Maven repo. > - We need a way to select classpath search strategy. E.g. we can add special > marker resource to NuGet package so that DLL understands that it is > NuGet-based. More investigation here is reuqired. > - Minimal set of required JARs should be defined. Currently we have over > >100Mb of Java libraries shipped with Ignite build. NuGet have limitation of > 30Mb per package. Only vital subset of JARs should be shipped. > *Infrastructure tasks* > - INFRA team must be asked about a place where NuGet package could be stored. > - Separate build plan should be created, producing NuGet artifacts. > *Marketing tasks* > - We need to produce clean, selling and intriguing header and description for > our package and attach logo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1870) Add aggregation function for Y axes values in TIME_LINE mode
[ https://issues.apache.org/jira/browse/IGNITE-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006394#comment-15006394 ] Alexey Kuznetsov edited comment on IGNITE-1870 at 11/16/15 9:33 AM: Added function name to value tooltip in TIME_LINE mode. was (Author: kuaw26): Added function to value tooltip in TIME_LINE mode. > Add aggregation function for Y axes values in TIME_LINE mode > > > Key: IGNITE-1870 > URL: https://issues.apache.org/jira/browse/IGNITE-1870 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov > Fix For: 1.5 > > > Add support for: First, Last, Min, Max, Avg, Sum, Count -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1870) Add aggregation function for Y axes values in TIME_LINE mode
[ https://issues.apache.org/jira/browse/IGNITE-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1870. -- Resolution: Fixed Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) Added function to value tooltip in TIME_LINE mode. > Add aggregation function for Y axes values in TIME_LINE mode > > > Key: IGNITE-1870 > URL: https://issues.apache.org/jira/browse/IGNITE-1870 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov > Fix For: 1.5 > > > Add support for: First, Last, Min, Max, Avg, Sum, Count -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1762) Chart settings should be preserved between chats type switch
[ https://issues.apache.org/jira/browse/IGNITE-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1762. -- Resolution: Fixed Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) Implemented saving settings for: # barChart -> [stacked/grouped] # areaChart -> [stacked / steam / expanded] P.S. this settings also saved to DB, but only after sql execute (when notebook saved). > Chart settings should be preserved between chats type switch > > > Key: IGNITE-1762 > URL: https://issues.apache.org/jira/browse/IGNITE-1762 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov > Fix For: 1.5 > > > In current implementation we simply recreate char every time we change chart > type (for example: bar chart -> pie chart), but for better user experience it > will be better to memorize current settings and restore them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1485. -- Assignee: (was: Pavel Konstantinov) Tested. > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1919) Blinking on Prev in load metadata dialog
Pavel Konstantinov created IGNITE-1919: -- Summary: Blinking on Prev in load metadata dialog Key: IGNITE-1919 URL: https://issues.apache.org/jira/browse/IGNITE-1919 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Priority: Minor To reproduce please do Prev in Load metadata dialog. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1904) Need to add two new dependencies in pom-file to cover special cases
[
https://issues.apache.org/jira/browse/IGNITE-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov closed IGNITE-1904.
--
Assignee: (was: Pavel Konstantinov)
Tested.
> Need to add two new dependencies in pom-file to cover special cases
> ---
>
> Key: IGNITE-1904
> URL: https://issues.apache.org/jira/browse/IGNITE-1904
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> If user added Generic JDBC and Secondary file system in cluster
> configuration, then the generated java-code contains two RED imports
> {code}
> import com.mchange.v2.c3p0.jboss.C3P0PooledDataSource;
> import org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem;
> {code}
> We need to add that dependencies to the pom-file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (IGNITE-1867) Fix java class names and package declaration
[ https://issues.apache.org/jira/browse/IGNITE-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reopened IGNITE-1867: Assignee: Vasiliy Sisko (was: Pavel Konstantinov) 1) C3P0PooledDataSource does not implement DataSource interface. 2) Snippet does not contain NearCacheConfiguration > Fix java class names and package declaration > > > Key: IGNITE-1867 > URL: https://issues.apache.org/jira/browse/IGNITE-1867 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Prachi Garg >Assignee: Vasiliy Sisko > Fix For: 1.5 > > > I noticed a few issues when I imported my project, created using the web > console, in IDEA - > 1. ServerConfigurationFactory class name is create in the file called > “ConfigurationFactory.java”. Class name and file name should be the same. > 2. The package declaration for ClientConfigurationFactory and > SeverConfigurationFactory classes is missing. > 3. There should be simple 'nodeStartup' class for starting a node, in the > IDE, using the XML configuration file. > 4. Missing near configuration for client in java code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
