[jira] [Created] (IGNITE-4066) NPE on access CacheJdbcPojoStoreFactory.getTypes()
Alexey Kuznetsov created IGNITE-4066: Summary: NPE on access CacheJdbcPojoStoreFactory.getTypes() Key: IGNITE-4066 URL: https://issues.apache.org/jira/browse/IGNITE-4066 Project: Ignite Issue Type: Bug Components: general Affects Versions: 1.6 Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Fix For: 1.8 Check that all places where CacheJdbcPojoStoreFactory.getTypes() invoked and fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-4065) Web console: Minimal size of elements on monitoring
[ https://issues.apache.org/jira/browse/IGNITE-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko closed IGNITE-4065. - > Web console: Minimal size of elements on monitoring > --- > > Key: IGNITE-4065 > URL: https://issues.apache.org/jira/browse/IGNITE-4065 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.8 >Reporter: Vasiliy Sisko > Fix For: 1.8 > > > Set minimal height of tables more than height of table header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4065) Web console: Minimal size of elements on monitoring
[ https://issues.apache.org/jira/browse/IGNITE-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-4065: - Assignee: (was: Vasiliy Sisko) > Web console: Minimal size of elements on monitoring > --- > > Key: IGNITE-4065 > URL: https://issues.apache.org/jira/browse/IGNITE-4065 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.8 >Reporter: Vasiliy Sisko > Fix For: 1.8 > > > Set minimal height of tables more than height of table header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4065) Web console: Minimal size of elements on monitoring
[ https://issues.apache.org/jira/browse/IGNITE-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko resolved IGNITE-4065. --- Resolution: Won't Fix > Web console: Minimal size of elements on monitoring > --- > > Key: IGNITE-4065 > URL: https://issues.apache.org/jira/browse/IGNITE-4065 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Maxim Afanasiev > Fix For: 1.8 > > > Set minimal height of tables more than height of table header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4065) Web console: Minimal size of elements on monitoring
[ https://issues.apache.org/jira/browse/IGNITE-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-4065: - Assignee: Vasiliy Sisko (was: Maxim Afanasiev) > Web console: Minimal size of elements on monitoring > --- > > Key: IGNITE-4065 > URL: https://issues.apache.org/jira/browse/IGNITE-4065 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko > Fix For: 1.8 > > > Set minimal height of tables more than height of table header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4065) Web console: Minimal size of elements on monitoring
Vasiliy Sisko created IGNITE-4065: - Summary: Web console: Minimal size of elements on monitoring Key: IGNITE-4065 URL: https://issues.apache.org/jira/browse/IGNITE-4065 Project: Ignite Issue Type: Bug Affects Versions: 1.8 Reporter: Vasiliy Sisko Assignee: Maxim Afanasiev Fix For: 1.8 Set minimal height of tables more than height of table header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4064) Web console: Clear filter functionality.
Vasiliy Sisko created IGNITE-4064: - Summary: Web console: Clear filter functionality. Key: IGNITE-4064 URL: https://issues.apache.org/jira/browse/IGNITE-4064 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.8 Reporter: Vasiliy Sisko Fix For: 1.8 # Add "X" button in right side of every non empty filter field to clear filter. # Clear filter on press of Esc button. Possible focus independent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4063) BinaryType.fieldNames() should return names in consistent order
Valentin Kulichenko created IGNITE-4063:
---
Summary: BinaryType.fieldNames() should return names in consistent
order
Key: IGNITE-4063
URL: https://issues.apache.org/jira/browse/IGNITE-4063
Project: Ignite
Issue Type: Bug
Components: binary
Affects Versions: 1.7
Reporter: Valentin Kulichenko
Priority: Critical
Fix For: 1.8
In some cases it can be useful to get the field names from metadata in the
order fields were written when the metadata was created (i.e. object was
serialized for the first time). For example, this can be used to recreate the
object using builder preserving the consistent field ordering, so that
{{BinaryObject.equals()}} method works properly.
Basically, we just need to replace {{HashMap}} with {{LinkedHashMap}} in the
{{BinaryType}} implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2413) Twitter streamer documentation is missing on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15569911#comment-15569911 ] Prachi Garg commented on IGNITE-2413: - http://apacheignite.gridgain.org/docs/twitter-streamer - added to v1.5, v1.6 and v1.7 > Twitter streamer documentation is missing on readme.io > -- > > Key: IGNITE-2413 > URL: https://issues.apache.org/jira/browse/IGNITE-2413 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Critical > Fix For: 1.8 > > > Twitter streamer was released as a part of 1.5. However there is no > documentation available on readme.io describing the new streaming > functionality. > Following documentation can be used as a reference > https://apacheignite.readme.io/docs/jms-data-streamer > https://apacheignite.readme.io/docs/flume-data-streamer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2413) Twitter streamer documentation is missing on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg closed IGNITE-2413. --- > Twitter streamer documentation is missing on readme.io > -- > > Key: IGNITE-2413 > URL: https://issues.apache.org/jira/browse/IGNITE-2413 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Critical > Fix For: 1.8 > > > Twitter streamer was released as a part of 1.5. However there is no > documentation available on readme.io describing the new streaming > functionality. > Following documentation can be used as a reference > https://apacheignite.readme.io/docs/jms-data-streamer > https://apacheignite.readme.io/docs/flume-data-streamer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4062) BinaryObject header should not participate in equals test
Valentin Kulichenko created IGNITE-4062:
---
Summary: BinaryObject header should not participate in equals test
Key: IGNITE-4062
URL: https://issues.apache.org/jira/browse/IGNITE-4062
Project: Ignite
Issue Type: Bug
Components: binary
Affects Versions: 1.7
Reporter: Valentin Kulichenko
Priority: Critical
Fix For: 1.8
{{BinaryObject.equals()}} compares the full byte array, which can give
incorrect results in come cases. For example, we sometimes write full class
name instead of type ID, so two objects that are equal from user's standpoint
will have different binary representation and {{equals()}} will return false.
We should make {{equals()}} implementation more smart and compare separately:
* type ID
* hash code
* portion of byte array that contains actual data, i.e. fields without header
and footer
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1118) AOP Based Grid Configuration Documentation Missing
[ https://issues.apache.org/jira/browse/IGNITE-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg closed IGNITE-1118. --- https://apacheignite.readme.io/docs/aop-based-grid-enabling > AOP Based Grid Configuration Documentation Missing > -- > > Key: IGNITE-1118 > URL: https://issues.apache.org/jira/browse/IGNITE-1118 > Project: Ignite > Issue Type: Bug >Reporter: Suminda Dharmasena >Assignee: Prachi Garg > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1118) AOP Based Grid Configuration Documentation Missing
[ https://issues.apache.org/jira/browse/IGNITE-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg resolved IGNITE-1118. - Resolution: Fixed > AOP Based Grid Configuration Documentation Missing > -- > > Key: IGNITE-1118 > URL: https://issues.apache.org/jira/browse/IGNITE-1118 > Project: Ignite > Issue Type: Bug >Reporter: Suminda Dharmasena >Assignee: Prachi Garg > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2413) Twitter streamer documentation is missing on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg resolved IGNITE-2413. - Resolution: Fixed > Twitter streamer documentation is missing on readme.io > -- > > Key: IGNITE-2413 > URL: https://issues.apache.org/jira/browse/IGNITE-2413 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Critical > Fix For: 1.8 > > > Twitter streamer was released as a part of 1.5. However there is no > documentation available on readme.io describing the new streaming > functionality. > Following documentation can be used as a reference > https://apacheignite.readme.io/docs/jms-data-streamer > https://apacheignite.readme.io/docs/flume-data-streamer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4034) Get rid of specialized methods in platform targets
[ https://issues.apache.org/jira/browse/IGNITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-4034. Resolution: Fixed > Get rid of specialized methods in platform targets > -- > > Key: IGNITE-4034 > URL: https://issues.apache.org/jira/browse/IGNITE-4034 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Most .NET -> Java calls go through common PlatformTarget InOut* methods. But > some simple operations have dedicated JNI calls, like PlatformCache.clear(). > Refactor these operations to use common methods to unify the logic and allow > interface separation in IGNITE-4027. > This will also reduce the amount of C++ code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4034) Get rid of specialized methods in platform targets
[ https://issues.apache.org/jira/browse/IGNITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-4034: -- Assignee: (was: Pavel Tupitsyn) > Get rid of specialized methods in platform targets > -- > > Key: IGNITE-4034 > URL: https://issues.apache.org/jira/browse/IGNITE-4034 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Most .NET -> Java calls go through common PlatformTarget InOut* methods. But > some simple operations have dedicated JNI calls, like PlatformCache.clear(). > Refactor these operations to use common methods to unify the logic and allow > interface separation in IGNITE-4027. > This will also reduce the amount of C++ code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4034) Get rid of specialized methods in platform targets
[ https://issues.apache.org/jira/browse/IGNITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15569238#comment-15569238 ] ASF GitHub Bot commented on IGNITE-4034: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1149 > Get rid of specialized methods in platform targets > -- > > Key: IGNITE-4034 > URL: https://issues.apache.org/jira/browse/IGNITE-4034 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Most .NET -> Java calls go through common PlatformTarget InOut* methods. But > some simple operations have dedicated JNI calls, like PlatformCache.clear(). > Refactor these operations to use common methods to unify the logic and allow > interface separation in IGNITE-4027. > This will also reduce the amount of C++ code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Tikhonov updated IGNITE-4052: - Description: In current implementation Ignite Mesos Framework connects to MESOS cluster via current user. Need to add ability to configure this parameters via system env properties. Also need to add properties for mesos role. See org/apache/ignite/mesos/IgniteFramework.java:537 was: In current implementation Ignite Mesos Framework connects to MESOS cluster via current user. Need to add ability to configure this parameters via system env properties. See org/apache/ignite/mesos/IgniteFramework.java:53 > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4030) Streamline PlatformTarget interface
[ https://issues.apache.org/jira/browse/IGNITE-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568983#comment-15568983 ] Pavel Tupitsyn commented on IGNITE-4030: Proposed method set: * InObjectStreamOutObjectStream - covers all cases. Estimated usages: 27 * InStreamOutStream - all cases without objects. Estimated usages: 91 * InLongOutLong - simple cases. Estimated usages: 49 > Streamline PlatformTarget interface > --- > > Key: IGNITE-4030 > URL: https://issues.apache.org/jira/browse/IGNITE-4030 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > 1) Review the set of inOut methods. There should be one uber-method which > takes a stream and an object, returns a stream and an object. This method > covers all use cases. Other methods should gradually simplify the signature. > 2) Provide a symmetrical callback method set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2356) IGFS client should be able to failover in case of server crash.
[ https://issues.apache.org/jira/browse/IGNITE-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568838#comment-15568838 ] Taras Ledkov edited comment on IGNITE-2356 at 10/12/16 2:15 PM: Fixed. [Tests|http://195.239.208.174/viewQueued.html?itemId=342134=queuedBuildOverviewTab] was (Author: tledkov-gridgain): Fixed > IGFS client should be able to failover in case of server crash. > --- > > Key: IGNITE-2356 > URL: https://issues.apache.org/jira/browse/IGNITE-2356 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Fix For: 2.0 > > > IGFS client (IgniteHadoopFileSystem) communicates IGFS over endpoint - either > TCP or shmem. > Only single endpoint can be specified. As such, should the server went down, > IgntieHadoopFileSystem (either new or existing) is no longer operational. > We need to let user specify several endpoints and failover/balance between > them. > Look at Hadoop HA first to get an ideas on how to configure multiple > addresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2356) IGFS client should be able to failover in case of server crash.
[ https://issues.apache.org/jira/browse/IGNITE-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568838#comment-15568838 ] Taras Ledkov commented on IGNITE-2356: -- Fixed > IGFS client should be able to failover in case of server crash. > --- > > Key: IGNITE-2356 > URL: https://issues.apache.org/jira/browse/IGNITE-2356 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Fix For: 2.0 > > > IGFS client (IgniteHadoopFileSystem) communicates IGFS over endpoint - either > TCP or shmem. > Only single endpoint can be specified. As such, should the server went down, > IgntieHadoopFileSystem (either new or existing) is no longer operational. > We need to let user specify several endpoints and failover/balance between > them. > Look at Hadoop HA first to get an ideas on how to configure multiple > addresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4061) Web Console: Add CacheJdbcPojoStoreFactory.SqlEscapeAll property
[ https://issues.apache.org/jira/browse/IGNITE-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-4061: - Summary: Web Console: Add CacheJdbcPojoStoreFactory.SqlEscapeAll property (was: Web Console: Add CacheJdbcPojoStoreFactory.SqlEscapeAll peroperty) > Web Console: Add CacheJdbcPojoStoreFactory.SqlEscapeAll property > > > Key: IGNITE-4061 > URL: https://issues.apache.org/jira/browse/IGNITE-4061 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.8 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.8 > > > In IGNITE-3938 CacheJdbcPojoStoreFactory.SqlEscapeAll peroperty was > implemented. We need to support this on Web Console Cache configuration > screen and in Java and XML generation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3961) IGFS: Support direct PROXY mode invocation in method: affinity
[
https://issues.apache.org/jira/browse/IGNITE-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568736#comment-15568736
]
Taras Ledkov commented on IGNITE-3961:
--
Fixed
> IGFS: Support direct PROXY mode invocation in method: affinity
> --
>
> Key: IGNITE-3961
> URL: https://issues.apache.org/jira/browse/IGNITE-3961
> Project: Ignite
> Issue Type: Sub-task
> Components: IGFS
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> See
> {{org.apache.ignite.hadoop.fs.v1.IgniteHadoopFileSystem.getFileBlockLocations}}
> for reference.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2355) Hadoop client should be able to failover in case of server crash.
[ https://issues.apache.org/jira/browse/IGNITE-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568739#comment-15568739 ] Taras Ledkov commented on IGNITE-2355: -- Fixed > Hadoop client should be able to failover in case of server crash. > - > > Key: IGNITE-2355 > URL: https://issues.apache.org/jira/browse/IGNITE-2355 > Project: Ignite > Issue Type: Sub-task > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: roadmap > Fix For: 1.8 > > > Currently we explicitly specify a single IP address of Ignite server for map > reduce. > If it goes down, no jobs can be submitted anymore. > Looks like we should give user ability to specify multiple addresses, and > failover between them. Our thin client (which underlies Hadoop client) is > already able to accept multiple addresses. > Look at Hadoop HA first to get an ideas on how to configure multiple > addresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3625) IGFS: Use common naming for IGFS meta and data caches.
[
https://issues.apache.org/jira/browse/IGNITE-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3625:
Fix Version/s: (was: 2.0)
1.8
> IGFS: Use common naming for IGFS meta and data caches.
> --
>
> Key: IGNITE-3625
> URL: https://issues.apache.org/jira/browse/IGNITE-3625
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> Currently IGFS is configured by passing names of two caches: meta and data.
> See {{FileSystemConfiguration.metaCacheName}} and
> {{FileSystemConfiguration.dataCacheName}}.
> These two caches are considered internal then and are not accessible for the
> user.
> We need to do the following during node startup:
> 1) If certain cache is configured as meta or data cache for multiple IGFS-es,
> or if it is configured as both meta and data cache for a single IGFS, then
> throw an exception.
> Relevant code pieces:
> {{IgfsProcessor.validateLocalIgfsConfigurations}}
> {{IgfsProcessorSelfTest}}.
> 2) During node startup change the name of this cache to
> {{igfs-IGFS_NAME-meta}} or {{igfs-IGFS_NAME-data}}. Change must be performed
> both inside IGFS config and cache config.
> Relevant code pieces:
> {{CacheConfiguration.name}}
> {{FileSystemConfiguration.metaCacheName}}
> {{FileSystemConfiguration.dataCacheName}}
> {{IgfsUtils.prepareCacheConfiguration}} - where change will be done.
> 3) If any of new names caches with any other cache name, an exception should
> be thrown. The most simple way: throw an exception if user-configured cache
> name starts with {{igfs-}} and ends with {{-meta}} or {{-data}}.
> Relevant code pieces:
> {{IgniteNamedInstance.initializeDefaultCacheConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4034) Get rid of specialized methods in platform targets
[ https://issues.apache.org/jira/browse/IGNITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4034: Assignee: Pavel Tupitsyn (was: Vladimir Ozerov) > Get rid of specialized methods in platform targets > -- > > Key: IGNITE-4034 > URL: https://issues.apache.org/jira/browse/IGNITE-4034 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Most .NET -> Java calls go through common PlatformTarget InOut* methods. But > some simple operations have dedicated JNI calls, like PlatformCache.clear(). > Refactor these operations to use common methods to unify the logic and allow > interface separation in IGNITE-4027. > This will also reduce the amount of C++ code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4034) Get rid of specialized methods in platform targets
[ https://issues.apache.org/jira/browse/IGNITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568563#comment-15568563 ] Vladimir Ozerov commented on IGNITE-4034: - Pavel, Looks good to me. Please make sure to double check the following before merge: 1) TC suites (.NET, CPP, ODBC); 2) Code style (esp. in Java). > Get rid of specialized methods in platform targets > -- > > Key: IGNITE-4034 > URL: https://issues.apache.org/jira/browse/IGNITE-4034 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Most .NET -> Java calls go through common PlatformTarget InOut* methods. But > some simple operations have dedicated JNI calls, like PlatformCache.clear(). > Refactor these operations to use common methods to unify the logic and allow > interface separation in IGNITE-4027. > This will also reduce the amount of C++ code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4060) RoundRobinLoadBalancingSpi doesn't work after client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov reassigned IGNITE-4060:
Assignee: Taras Ledkov
> RoundRobinLoadBalancingSpi doesn't work after client reconnect.
> ---
>
> Key: IGNITE-4060
> URL: https://issues.apache.org/jira/browse/IGNITE-4060
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
> Attachments: RoundRodbinErrorReproducer.java
>
>
> If {{IgntieCompute.apply()}} is called on a client after reconnect, it fails.
> Reproducer code is attached. The problem is that
> {{RoundRobinLoadBalancingSpi}} (which is default one) is not notified about
> topology reset.
> Sample stack trace:
> {code}
> class org.apache.ignite.IgniteException: Task topology does not have alive
> nodes: [TcpDiscoveryNode [id=50f56f53-bbf6-4d66-bfc5-02d801241e14,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1476269284697, loc=false,
> ver=1.7.0#19700101-sha1:, isClient=false]]
> at
> org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinGlobalLoadBalancer.checkBalancerNodes(RoundRobinGlobalLoadBalancer.java:256)
> at
> org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinGlobalLoadBalancer.getBalancedNode(RoundRobinGlobalLoadBalancer.java:201)
> at
> org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpi.getBalancedNode(RoundRobinLoadBalancingSpi.java:307)
> at
> org.apache.ignite.internal.managers.loadbalancer.GridLoadBalancerManager.getBalancedNode(GridLoadBalancerManager.java:81)
> at
> org.apache.ignite.internal.managers.loadbalancer.GridLoadBalancerManager$1.getBalancedNode(GridLoadBalancerManager.java:99)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$T8.map(GridClosureProcessor.java:1616)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$T8.map(GridClosureProcessor.java:1587)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$2.call(GridTaskWorker.java:519)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$2.call(GridTaskWorker.java:517)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6509)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:516)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:679)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:403)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:630)
> at
> org.apache.ignite.internal.IgniteComputeImpl.apply(IgniteComputeImpl.java:451)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[
https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565753#comment-15565753
]
Pavel Tupitsyn edited comment on IGNITE-1915 at 10/12/16 11:20 AM:
---
1,2) Reverted (temp code)
3) Fixed
4) Done (local flag + get before putIfAbsent)
5,6,7) Done
8) Primary node check added instead
was (Author: ptupitsyn):
1,2) Reverted (temp code)
3) Fixed
4) This does not make sense to me. Do you mean that
{code}if (get() == null) then putIfAbsent(){code}
is faster than plain
{code}putIfAbsent(){code}? I expect putIfAbsent to be as efficient as possible
by itself.
5,6,7) Done
8) Which modes will be correct?
> .NET: Ignite as Entity Framework Second-Level Cache
> ---
>
> Key: IGNITE-1915
> URL: https://issues.apache.org/jira/browse/IGNITE-1915
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Entity Framework is #1 ORM for .NET
> We should provide easy solution to boost Entity Framework performance with
> Ignite.
> EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in
> one, EF6 requies more customization or a 3rd party lib like
> https://efcache.codeplex.com/). For now, let's do EF6 only.
> This should be in a separate assembly and a separate NuGet package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4060) RoundRobinLoadBalancingSpi doesn't work after client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4060:
Attachment: RoundRodbinErrorReproducer.java
> RoundRobinLoadBalancingSpi doesn't work after client reconnect.
> ---
>
> Key: IGNITE-4060
> URL: https://issues.apache.org/jira/browse/IGNITE-4060
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
> Fix For: 1.8
>
> Attachments: RoundRodbinErrorReproducer.java
>
>
> If {{IgntieCompute.apply()}} is called on a client after reconnect, it fails.
> Reproducer code is attached. The problem is that
> {{RoundRobinLoadBalancingSpi}} (which is default one) is not notified about
> topology reset.
> Sample stack trace:
> {code}
> class org.apache.ignite.IgniteException: Task topology does not have alive
> nodes: [TcpDiscoveryNode [id=50f56f53-bbf6-4d66-bfc5-02d801241e14,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1476269284697, loc=false,
> ver=1.7.0#19700101-sha1:, isClient=false]]
> at
> org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinGlobalLoadBalancer.checkBalancerNodes(RoundRobinGlobalLoadBalancer.java:256)
> at
> org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinGlobalLoadBalancer.getBalancedNode(RoundRobinGlobalLoadBalancer.java:201)
> at
> org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpi.getBalancedNode(RoundRobinLoadBalancingSpi.java:307)
> at
> org.apache.ignite.internal.managers.loadbalancer.GridLoadBalancerManager.getBalancedNode(GridLoadBalancerManager.java:81)
> at
> org.apache.ignite.internal.managers.loadbalancer.GridLoadBalancerManager$1.getBalancedNode(GridLoadBalancerManager.java:99)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$T8.map(GridClosureProcessor.java:1616)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$T8.map(GridClosureProcessor.java:1587)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$2.call(GridTaskWorker.java:519)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$2.call(GridTaskWorker.java:517)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6509)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:516)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:679)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:403)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:630)
> at
> org.apache.ignite.internal.IgniteComputeImpl.apply(IgniteComputeImpl.java:451)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4060) RoundRobinLoadBalancingSpi doesn't work after client reconnect.
Vladimir Ozerov created IGNITE-4060:
---
Summary: RoundRobinLoadBalancingSpi doesn't work after client
reconnect.
Key: IGNITE-4060
URL: https://issues.apache.org/jira/browse/IGNITE-4060
Project: Ignite
Issue Type: Bug
Components: compute
Affects Versions: 1.7
Reporter: Vladimir Ozerov
Fix For: 1.8
Attachments: RoundRodbinErrorReproducer.java
If {{IgntieCompute.apply()}} is called on a client after reconnect, it fails.
Reproducer code is attached. The problem is that {{RoundRobinLoadBalancingSpi}}
(which is default one) is not notified about topology reset.
Sample stack trace:
{code}
class org.apache.ignite.IgniteException: Task topology does not have alive
nodes: [TcpDiscoveryNode [id=50f56f53-bbf6-4d66-bfc5-02d801241e14,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1476269284697, loc=false,
ver=1.7.0#19700101-sha1:, isClient=false]]
at
org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinGlobalLoadBalancer.checkBalancerNodes(RoundRobinGlobalLoadBalancer.java:256)
at
org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinGlobalLoadBalancer.getBalancedNode(RoundRobinGlobalLoadBalancer.java:201)
at
org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpi.getBalancedNode(RoundRobinLoadBalancingSpi.java:307)
at
org.apache.ignite.internal.managers.loadbalancer.GridLoadBalancerManager.getBalancedNode(GridLoadBalancerManager.java:81)
at
org.apache.ignite.internal.managers.loadbalancer.GridLoadBalancerManager$1.getBalancedNode(GridLoadBalancerManager.java:99)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$T8.map(GridClosureProcessor.java:1616)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$T8.map(GridClosureProcessor.java:1587)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$2.call(GridTaskWorker.java:519)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$2.call(GridTaskWorker.java:517)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6509)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:516)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:679)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:403)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:630)
at
org.apache.ignite.internal.IgniteComputeImpl.apply(IgniteComputeImpl.java:451)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-4055) Web console: Cluster cache key configurations do not have remove button.
[ https://issues.apache.org/jira/browse/IGNITE-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-4055. -- Assignee: (was: Pavel Konstantinov) > Web console: Cluster cache key configurations do not have remove button. > > > Key: IGNITE-4055 > URL: https://issues.apache.org/jira/browse/IGNITE-4055 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4059) Web console: Error in log on break of animation.
Vasiliy Sisko created IGNITE-4059: - Summary: Web console: Error in log on break of animation. Key: IGNITE-4059 URL: https://issues.apache.org/jira/browse/IGNITE-4059 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.8 Reporter: Vasiliy Sisko Fix For: 1.8 angular.js:13920 TypeError: Cannot read property 'on' of null at Object.TooltipFactoryDecorated.config.onShow (tooltip.js:31) at enterAnimateCallback (angular-strap.js:553) at processQueue (angular.js:16383) at angular.js:16399 at Scope.$eval (angular.js:17682) at Scope.$digest (angular.js:17495) at Scope.$apply (angular.js:17790) at HTMLElement. (angular.js:25890) at HTMLElement.dispatch (jquery.js:5201) at HTMLElement.elemData.handle (jquery.js:5009) To reproduce: # F.e. add some type in Type configurations table on Binary configuration section of cluster. # Remove added type by click on "X" button when tooltip show animation in progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4055) Web console: Cluster cache key configurations do not have remove button.
[ https://issues.apache.org/jira/browse/IGNITE-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-4055: - Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) > Web console: Cluster cache key configurations do not have remove button. > > > Key: IGNITE-4055 > URL: https://issues.apache.org/jira/browse/IGNITE-4055 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3961) IGFS: Support direct PROXY mode invocation in method: affinity
[
https://issues.apache.org/jira/browse/IGNITE-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568095#comment-15568095
]
Taras Ledkov commented on IGNITE-3961:
--
Test for resource injection to a secondary FS is added. Review issues are fixed.
> IGFS: Support direct PROXY mode invocation in method: affinity
> --
>
> Key: IGNITE-3961
> URL: https://issues.apache.org/jira/browse/IGNITE-3961
> Project: Ignite
> Issue Type: Sub-task
> Components: IGFS
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> See
> {{org.apache.ignite.hadoop.fs.v1.IgniteHadoopFileSystem.getFileBlockLocations}}
> for reference.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[ https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568093#comment-15568093 ] Anton Vinogradov commented on IGNITE-3303: -- Update. According to https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute each contribution should be checked before review. I found no runs of "Ignite Streamers" at TeamCity, also, new tests suite was to added to this TeamCity task. I've added FlinkIgniteSourceSelfTestSuite and checked result As you can see, TC shows same failure http://ci.ignite.apache.org/viewLog.html?buildId=330384=buildResultsDiv=IgniteTests_IgniteStreamers > Apache Flink Integration - Flink source to run a continuous query against one > or multiple caches > > > Key: IGNITE-3303 > URL: https://issues.apache.org/jira/browse/IGNITE-3303 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra > Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, > testFlinkIgniteSourceWithLargeBatch.log, win7.PNG > > > Apache Flink integration > +++ *Ignite as a bidirectional Connector* +++ > As a Flink source => run a continuous query against one or multiple > caches [4]. > Related discussion : > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4058) Divide JVM_OPTS in yardstick properies file
Sergey Kozlov created IGNITE-4058: - Summary: Divide JVM_OPTS in yardstick properies file Key: IGNITE-4058 URL: https://issues.apache.org/jira/browse/IGNITE-4058 Project: Ignite Issue Type: Task Components: yardstick Affects Versions: 1.7 Reporter: Sergey Kozlov Yardstick properties file has only JVM_OPTS parameter applied to both server and driver nodes. But due logic of some load tests and benchmarks we need to pass different parameters for servers and drivers line heap size (-Xmx, -Xms). I suggest to introduce DRIVER_JVM_OPTS and SERVER_JVM_OPTS. JVM_OPTS should be included into both new parameters and becomes the parameter of general JVM options. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4057) Web Console: Add proper icons to all modals
Alexey Kuznetsov created IGNITE-4057: Summary: Web Console: Add proper icons to all modals Key: IGNITE-4057 URL: https://issues.apache.org/jira/browse/IGNITE-4057 Project: Ignite Issue Type: Task Components: wizards Affects Versions: 1.7 Reporter: Alexey Kuznetsov Fix For: 1.8 For usability reasons it will be nice to show some icon in modals header. For example: # if modal ask for something - show (?) # if modal show some info - show (i) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-514) Need to lock entries in ATOMIC cache only when doing batch store update
[ https://issues.apache.org/jira/browse/IGNITE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev reassigned IGNITE-514: -- Assignee: Dmitry Karachentsev > Need to lock entries in ATOMIC cache only when doing batch store update > --- > > Key: IGNITE-514 > URL: https://issues.apache.org/jira/browse/IGNITE-514 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Gura >Assignee: Dmitry Karachentsev > > 1. Lock all entries only if store enabled and batch update is true > 2. Lock entries in natural order if keys are comparable, otherwise serialize > keys and sort serialized byte arrays. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-4056) Web console: Cluster cache key configurations do not have remove button.
[ https://issues.apache.org/jira/browse/IGNITE-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko closed IGNITE-4056. - > Web console: Cluster cache key configurations do not have remove button. > > > Key: IGNITE-4056 > URL: https://issues.apache.org/jira/browse/IGNITE-4056 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3054) Rework client connection handling from thread-per-client to NIO model.
[ https://issues.apache.org/jira/browse/IGNITE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568031#comment-15568031 ] Dmitry Karachentsev commented on IGNITE-3054: - Semen, thanks for review, added your recommendations to onDisconnected() method. The case you worry about could happen only if message was received for disconnected client, so we can simply drop it (I've added new check). This behavior is provided by connection logic that will not add new worker if there was not stopped current one. Also I need access to worker from listener, because there are operations that require to change it's state. > Rework client connection handling from thread-per-client to NIO model. > -- > > Key: IGNITE-3054 > URL: https://issues.apache.org/jira/browse/IGNITE-3054 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov >Assignee: Dmitry Karachentsev > Fix For: 1.8 > > > Currently both servers and clients has the same operational model - > thread-per-connection. While being more or less fine for servers, this could > be a problem for clients when their total number is too high (e.g. 1000 or > even more). > We should rework client handling model and employ standard NIO technique: one > or several acceptor threads + thread pool to server requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4056) Web console: Cluster cache key configurations do not have remove button.
[ https://issues.apache.org/jira/browse/IGNITE-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko resolved IGNITE-4056. --- Resolution: Duplicate > Web console: Cluster cache key configurations do not have remove button. > > > Key: IGNITE-4056 > URL: https://issues.apache.org/jira/browse/IGNITE-4056 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[ https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15567961#comment-15567961 ] Anton Vinogradov commented on IGNITE-3303: -- Saikat, There is no reason to validate, because fail already proven at 2 different PCs. Please analize attached thread dump to reproduce and fix. Possible, you just need to increase keys amount and timeout to reproduce it. > Apache Flink Integration - Flink source to run a continuous query against one > or multiple caches > > > Key: IGNITE-3303 > URL: https://issues.apache.org/jira/browse/IGNITE-3303 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra > Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, > testFlinkIgniteSourceWithLargeBatch.log, win7.PNG > > > Apache Flink integration > +++ *Ignite as a bidirectional Connector* +++ > As a Flink source => run a continuous query against one or multiple > caches [4]. > Related discussion : > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3731) Web Console: Add fetch first page only for query on SQL screen
[ https://issues.apache.org/jira/browse/IGNITE-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15567942#comment-15567942 ] Andrey Novikov edited comment on IGNITE-3731 at 10/12/16 7:44 AM: -- Not work as expected for: export all, refresh rate. Need fix vertical align checkbox. Fixed ui and tooltips. was (Author: anovikov): Not work as expected for: export all, refresh rate. > Web Console: Add fetch first page only for query on SQL screen > -- > > Key: IGNITE-3731 > URL: https://issues.apache.org/jira/browse/IGNITE-3731 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Andrey Novikov >Assignee: Maxim Afanasiev >Priority: Minor > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4055) Web console: Cluster cache key configurations do not have remove button.
Vasiliy Sisko created IGNITE-4055: - Summary: Web console: Cluster cache key configurations do not have remove button. Key: IGNITE-4055 URL: https://issues.apache.org/jira/browse/IGNITE-4055 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.8 Reporter: Vasiliy Sisko Fix For: 1.8 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4056) Web console: Cluster cache key configurations do not have remove button.
Vasiliy Sisko created IGNITE-4056: - Summary: Web console: Cluster cache key configurations do not have remove button. Key: IGNITE-4056 URL: https://issues.apache.org/jira/browse/IGNITE-4056 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.8 Reporter: Vasiliy Sisko Fix For: 1.8 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4048) Web console: result panel is not displayed in case if first query is incorrect
[ https://issues.apache.org/jira/browse/IGNITE-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-4048: --- Summary: Web console: result panel is not displayed in case if first query is incorrect (was: Web console: result panel doesn't show in case if first query is incorrect) > Web console: result panel is not displayed in case if first query is incorrect > -- > > Key: IGNITE-4048 > URL: https://issues.apache.org/jira/browse/IGNITE-4048 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov > > Create a new Query > Write 'select * from qwerty' > Execute > Observed: there is no result panel with error message below the query area. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
