[jira] [Updated] (IGNITE-802) [Test] [Rare] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-802: --- Assignee: (was: Denis Magda) > [Test] [Rare] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > -- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5.0.final >Reporter: Artem Shutak > Labels: Muted_test > Fix For: 1.8 > > Attachments: > Ignite_Tests_Ignite_Binary_Objects_Data_Strucutures_268_artifacts.zip, > ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2552) Eviction policy must consider either max size or max entries count
[ https://issues.apache.org/jira/browse/IGNITE-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2552: Priority: Major (was: Critical) > Eviction policy must consider either max size or max entries count > -- > > Key: IGNITE-2552 > URL: https://issues.apache.org/jira/browse/IGNITE-2552 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 1.8 > > > Presently both max size and max entries number are considered by eviction > policy logic even if the only one is set by user explicitly. > This behavior must be reworked in a way that if one of the parameters is set > explicitly then only it will be used by eviction policy while the other one > will be ignored. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3501) Step-by-step guidance on how to configure and use binary types across Java and .Net
[ https://issues.apache.org/jira/browse/IGNITE-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3501: Priority: Major (was: Critical) > Step-by-step guidance on how to configure and use binary types across Java > and .Net > --- > > Key: IGNITE-3501 > URL: https://issues.apache.org/jira/browse/IGNITE-3501 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 1.6 >Reporter: Denis Magda >Assignee: Denis Magda > Labels: .net > Fix For: 1.8 > > > It's quite a common task and endeavor to work with objects, stored in Ignite > caches, in their deserialized form on Java and .Net sides. This requires > special setup at the configuration level. Presently we don't have a page that > list this particular steps with examples. > The following can be used as a draft > 1) Explicitly configure all your custom types on Java side using > BinaryConfiguration.typeConfigurations property [1] or > BinaryConfiguration.classNames property [2]. > 2) Explicitly configure the same corresponding .Net types on .Net side using > PlatformDotNetBinaryConfiguration.types property as it shown under XML tab on > this page [3]. Remove BinaryConfiguration bean from .Net XML configuration if > you use it before. Set additional required properties to > PlatformDotNetBinaryConfiguration bean if BinaryConfiguration used any. > 3) If you use custom keys then make sure that both "hashCode" and "equals" > methods are implemented properly on both Java and .Net ends. > 4) On .Net side you should implement IBinarizable interface [4] or go with > Ignite Reflective Serialization [5] for your custom objects. > 5) On Java side you can implement Binarizable interface as well or rely on > reflective serialization making sure that your objects don't implement > Externalizable interface and don't override readObject/writeObject methods > [6]. > Please let me know if everything works fine on your side after applying the > listed steps. > Regards, > Denis > [1] > https://apacheignite.readme.io/docs/binary-marshaller#configuring-binary-objects > [2] > https://ignite.apache.org/releases/1.6.0/javadoc/org/apache/ignite/configuration/BinaryConfiguration.html#setClassNames(java.util.Collection) > [3] https://apacheignite-net.readme.io/docs/serialization#ibinarizable > [4] https://apacheignite-net.readme.io/docs/serialization#ibinarizable > [5] > https://apacheignite-net.readme.io/docs/serialization#ignite-reflective-serialization > [6] https://apacheignite.readme.io/docs/binary-marshaller#basic-concepts > On .Net side the configuration must be provided for App.config, C# config and > Spring XML. > On Java side the configuration must be provided for Java and Spring XML > configs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2656) Documentation on debugging and fixing the reasons of node disconnection from the cluster
[
https://issues.apache.org/jira/browse/IGNITE-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-2656:
Priority: Minor (was: Major)
> Documentation on debugging and fixing the reasons of node disconnection from
> the cluster
>
>
> Key: IGNITE-2656
> URL: https://issues.apache.org/jira/browse/IGNITE-2656
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Minor
> Fix For: 1.8
>
>
> Sometimes a node can be abruptly kicked off from the cluster buy some reason.
> The documentation must contain information on how to get to the root of the
> issue by looking at logs files. Usually the node that was kicked off contains
> "Local node segmented" message and the node that failed its next neighbor
> contains a message with more details "Failed to send message to next node".
> Next the article must list possible reasons of the disconnection:
> - long GC pauses. Give recommendations on how to check;
> - high node utilization so that it responds with a delay;
> - low network configuration parameters that are not suited for an environment;
> There should be a section about
> {{IgniteConfiguration.failureDetectionTimeout}} describing its behavior and
> showing all its pros and cons.
> The article must say when it makes sense to 'disable' this timeout by
> switching to explicit configuration of TcpDiscoverySpi.socketTimeout,
> TcpDiscoverySpi.ackTimeout, TcpDiscoverySpi.maxAckTimeout,
> TcpDiscoverySpi.reconnectCount. Pros and cons of manual configuration has to
> be mentioned as well.
>
> Also I would list the usage of TcpDiscoverySpi.joinTimeout,
> TcpDiscoverySpi.networkTimeout (used on client reconnect, servers waits for
> join result, node stop, socket reader first message.) there as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3723) Web console staging: there are absent fields on Import model from DB dialog
[ https://issues.apache.org/jira/browse/IGNITE-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Afanasiev resolved IGNITE-3723. - Resolution: Resolved Assignee: Andrey Novikov (was: Maxim Afanasiev) Fixed please review. > Web console staging: there are absent fields on Import model from DB dialog > --- > > Key: IGNITE-3723 > URL: https://issues.apache.org/jira/browse/IGNITE-3723 > Project: Ignite > Issue Type: Bug > Components: UI >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov >Priority: Minor > Attachments: ig-3723.png > > > Please see attachment -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3729) Web Console: Rework form layout
Maxim Afanasiev created IGNITE-3729: --- Summary: Web Console: Rework form layout Key: IGNITE-3729 URL: https://issues.apache.org/jira/browse/IGNITE-3729 Project: Ignite Issue Type: Task Components: wizards Reporter: Maxim Afanasiev Priority: Minor Fix For: 1.8 Need to rework form layout. Abandon the use of col-xx classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3005) visorcmd: we need to improve alert command
[
https://issues.apache.org/jira/browse/IGNITE-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov closed IGNITE-3005.
Merged to master.
> visorcmd: we need to improve alert command
> --
>
> Key: IGNITE-3005
> URL: https://issues.apache.org/jira/browse/IGNITE-3005
> Project: Ignite
> Issue Type: Improvement
> Components: visor
>Affects Versions: 1.5.0.final
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Trivial
> Fix For: 1.8
>
>
> Presently per-node alert prints in log it's info without node ID and user
> cannot understand on what node that alert was triggered.
> {code}
> 04/14/16, 15:06:01 | Alert [id=a8874c91(@a5), spec=-r -t=10 -hu=gt10, created
> on=04/14/16, 14:59:19]
> {code}
> So we need to print out node ID8 in alert info for per-node alerts.
> {code}
> 04/14/16, 15:06:01 | Alert [id=a8874c91(@a5), nid8=12345678, spec=-r -t=10
> -hu=gt10, created on=04/14/16, 14:59:19]
> {code}
> Also will be useful to print out Node IP the same which we printing in 'node'
> command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3728) Lost documentation for Cassandra module
[ https://issues.apache.org/jira/browse/IGNITE-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433797#comment-15433797 ] Denis Magda commented on IGNITE-3728: - [~pgarg], looks like you lost a portion of Cassandra documentation at the time 1.7 were being prepared to become the latest one. Please fix this. > Lost documentation for Cassandra module > --- > > Key: IGNITE-3728 > URL: https://issues.apache.org/jira/browse/IGNITE-3728 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 1.7 >Reporter: Igor Rudyak >Assignee: Prachi Garg > > After switching from Ignite version 1.6 to 1.7 it was lost some portion of > the official documentation on readme.io. For example all the documentation > for Cassandra module is only available for version 1.6: > https://apacheignite.readme.io/v1.6/docs/overview > but not for 1.7 which is now current -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3728) Lost documentation for Cassandra module
[ https://issues.apache.org/jira/browse/IGNITE-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3728: Assignee: Prachi Garg > Lost documentation for Cassandra module > --- > > Key: IGNITE-3728 > URL: https://issues.apache.org/jira/browse/IGNITE-3728 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 1.7 >Reporter: Igor Rudyak >Assignee: Prachi Garg > > After switching from Ignite version 1.6 to 1.7 it was lost some portion of > the official documentation on readme.io. For example all the documentation > for Cassandra module is only available for version 1.6: > https://apacheignite.readme.io/v1.6/docs/overview > but not for 1.7 which is now current -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3728) Lost documentation for Cassandra module
Igor Rudyak created IGNITE-3728: --- Summary: Lost documentation for Cassandra module Key: IGNITE-3728 URL: https://issues.apache.org/jira/browse/IGNITE-3728 Project: Ignite Issue Type: Bug Components: documentation Affects Versions: 1.7 Reporter: Igor Rudyak After switching from Ignite version 1.6 to 1.7 it was lost some portion of the official documentation on readme.io. For example all the documentation for Cassandra module is only available for version 1.6: https://apacheignite.readme.io/v1.6/docs/overview but not for 1.7 which is now current -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2680) Terminating running SQL queries
[
https://issues.apache.org/jira/browse/IGNITE-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-2680:
Assignee: Sergi Vladykin (was: Alexei Scherbakov)
> Terminating running SQL queries
> ---
>
> Key: IGNITE-2680
> URL: https://issues.apache.org/jira/browse/IGNITE-2680
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Sergi Vladykin
> Labels: important
>
> If to start a long running SQL query over a huge cache will millions of
> entries there should be a way terminate it. Even if {{QueryCursor}} is closed
> the query won't be cancelled consuming available resources.
> There should be a way to close a query having using an object that is related
> to it. Seems that ideally we can use {{QueryCursor.close()}} method for that;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3633) Throw an exception when binary object without explicitly set hash code is used as a key
[ https://issues.apache.org/jira/browse/IGNITE-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3633: Assignee: Alexander Paschenko (was: Denis Magda) > Throw an exception when binary object without explicitly set hash code is > used as a key > --- > > Key: IGNITE-3633 > URL: https://issues.apache.org/jira/browse/IGNITE-3633 > Project: Ignite > Issue Type: Task > Components: binary, cache, SQL >Reporter: Alexander Paschenko >Assignee: Alexander Paschenko > Fix For: 1.8 > > > New binary built keys erroneously get put to cache as having cache code of 0. > We want to force user to set hash code explicitly by throwing an exception > when they do not do so. > Proposed solution by Denis Magda: > http://apache-ignite-developers.2346864.n4.nabble.com/All-BinaryObjects-created-by-BinaryObjectBuilder-stored-at-the-same-partition-by-default-td8042i20.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2560) Support injections in entry processors
[
https://issues.apache.org/jira/browse/IGNITE-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432965#comment-15432965
]
Andrew Mashenkov edited comment on IGNITE-2560 at 8/23/16 3:01 PM:
---
Hi, Semen
{quote}
I can't find test for invokeAll(Map> map, Object... args)', could you please point me where it was added?
{quote}
See class _GridCacheAbstractFullApiSelfTest_. Method
_testTransformResourceInjection_ calls _doTransformResourceInjection_ with
cache and cache-with-async. Method _doTransformResourceInjection_ make checks
with _invoke_, _invokeAll_, _invokeAll (Map ...)_.
{quote}
in GridLocalAtomicCache let's do not use wrapper at all, instead just call
GridResourceProcessor.inject on entry processor
{quote}
Please, take a look at method _invokeAllAsync_ in GridLocalAtomicCache class.
Method signature tells it throws *no* exceptions, but
_resourceProcessor.inject(..)_ does. Whether exception is being processed
correctly?
was (Author: amashenkov):
Hi, Semen
{quote}
I can't find test for invokeAll(Map> map, Object... args)', could you please point me where it was added?
{quote}
See class _GridCacheAbstractFullApiSelfTest_. Method
_testTransformResourceInjection_ calls _doTransformResourceInjection_ with
cache and cache-with-async. Method _doTransformResourceInjection_ make checks
with _invoke_, _invokeAll_, _invokeAll (Map ...)_.
{quote}
in GridLocalAtomicCache let's do not use wrapper at all, instead just call
GridResourceProcessor.inject on entry processor
{quote}
Please, take a look on method _invokeAllAsync_ in GridLocalAtomicCache class.
Method signature tells it throws *no* exceptions, but
_resourceProcessor.inject(..)_ does. Whether exception is being processed
correctly?
> Support injections in entry processors
> --
>
> Key: IGNITE-2560
> URL: https://issues.apache.org/jira/browse/IGNITE-2560
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> Currently resources are not injected in entry processor, which is not
> consistent with other functionality, like closures, jobs, listeners, etc.
> To avoid performance degradation we should introspect the class only once,
> cache this information and do not try to inject if there are no annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2560) Support injections in entry processors
[
https://issues.apache.org/jira/browse/IGNITE-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432965#comment-15432965
]
Andrew Mashenkov commented on IGNITE-2560:
--
Hi, Semen
{quote}
I can't find test for invokeAll(Map> map, Object... args)', could you please point me where it was added?
{quote}
See class _GridCacheAbstractFullApiSelfTest_. Method
_testTransformResourceInjection_ calls _doTransformResourceInjection_ with
cache and cache-with-async. Method _doTransformResourceInjection_ make checks
with _invoke_, _invokeAll_, _invokeAll (Map ...)_.
{quote}
in GridLocalAtomicCache let's do not use wrapper at all, instead just call
GridResourceProcessor.inject on entry processor
{quote}
Please, take a look on method _invokeAllAsync_ in GridLocalAtomicCache class.
Method signature tells it throws *no* exceptions, but
_resourceProcessor.inject(..)_ does. Whether exception is being processed
correctly?
> Support injections in entry processors
> --
>
> Key: IGNITE-2560
> URL: https://issues.apache.org/jira/browse/IGNITE-2560
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> Currently resources are not injected in entry processor, which is not
> consistent with other functionality, like closures, jobs, listeners, etc.
> To avoid performance degradation we should introspect the class only once,
> cache this information and do not try to inject if there are no annotations.
--
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=15432898#comment-15432898 ] Pavel Tupitsyn edited comment on IGNITE-1915 at 8/23/16 2:40 PM: - Considerations: 1) Introduce multiple caching strategies, similar to Hibernate: * Read-only. Very simple, the fastest. No invalidation. * Non-strict read-write. Only one writer is expected at the moment. * Strict read-write. We can implement strict read-write strategy as a separate ticket. 2) Get rid of EFCache dependency and implement the boilerplate ourselves. This will allow more control over query execution. was (Author: ptupitsyn): I think we should introduce multiple caching strategies, similar to Hibernate: * Read-only. Very simple, the fastest. No invalidation. * Non-strict read-write. Only one writer is expected at the moment. * Strict read-write. We can implement strict read-write strategy as a separate ticket. > .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: Vladimir Ozerov > 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] [Commented] (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=15432898#comment-15432898 ] Pavel Tupitsyn commented on IGNITE-1915: I think we should introduce multiple caching strategies, similar to Hibernate: * Read-only. Very simple, the fastest. No invalidation. * Non-strict read-write. Only one writer is expected at the moment. * Strict read-write. We can implement strict read-write strategy as a separate ticket. > .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: Vladimir Ozerov > 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] [Created] (IGNITE-3727) ignite.message() method not support async mode,withAsync() is invalid.
Yujue Li created IGNITE-3727: Summary: ignite.message() method not support async mode,withAsync() is invalid. Key: IGNITE-3727 URL: https://issues.apache.org/jira/browse/IGNITE-3727 Project: Ignite Issue Type: Bug Components: messaging Affects Versions: 1.7 Environment: windows 7 Reporter: Yujue Li Priority: Blocker Fix For: 1.8 ignite.message() method not support async mode,withAsync() is invalid. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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=15432749#comment-15432749 ] Pavel Tupitsyn commented on IGNITE-1915: Merged with master > .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: Vladimir Ozerov > 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] [Closed] (IGNITE-3325) .NET: Improve CompiledQuery in LINQ provider
[
https://issues.apache.org/jira/browse/IGNITE-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn closed IGNITE-3325.
--
> .NET: Improve CompiledQuery in LINQ provider
>
>
> Key: IGNITE-3325
> URL: https://issues.apache.org/jira/browse/IGNITE-3325
> Project: Ignite
> Issue Type: Bug
> Components: community, platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net
> Fix For: 1.8
>
>
> User reported that the following code fails with "Error compiling query: all
> compiled query arguments should come from enclosing delegate parameters."
> {code}
> Func>> qry =
> CompiledQuery.Compile((int x, int y,int z) =>
> orderCache.AsCacheQueryable().Where(e => e.Value.OrderId % x == z).Take(y));
> {code}
> Other limitations are:
> * Embedded parameters are not supported
> * Maximum number of parameters is 8
> We should provide additional additional method to compile a delegate which
> takes an array of args.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3325) .NET: Improve CompiledQuery in LINQ provider
[
https://issues.apache.org/jira/browse/IGNITE-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432637#comment-15432637
]
Pavel Tupitsyn commented on IGNITE-3325:
Merged to master.
> .NET: Improve CompiledQuery in LINQ provider
>
>
> Key: IGNITE-3325
> URL: https://issues.apache.org/jira/browse/IGNITE-3325
> Project: Ignite
> Issue Type: Bug
> Components: community, platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net
> Fix For: 1.8
>
>
> User reported that the following code fails with "Error compiling query: all
> compiled query arguments should come from enclosing delegate parameters."
> {code}
> Func>> qry =
> CompiledQuery.Compile((int x, int y,int z) =>
> orderCache.AsCacheQueryable().Where(e => e.Value.OrderId % x == z).Take(y));
> {code}
> Other limitations are:
> * Embedded parameters are not supported
> * Maximum number of parameters is 8
> We should provide additional additional method to compile a delegate which
> takes an array of args.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3693) IgfsLocalSecondaryFileSystemDualAsyncSelfTest.testFormat fails.
[
https://issues.apache.org/jira/browse/IGNITE-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432636#comment-15432636
]
ASF GitHub Bot commented on IGNITE-3693:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/960
> IgfsLocalSecondaryFileSystemDualAsyncSelfTest.testFormat fails.
> ---
>
> Key: IGNITE-3693
> URL: https://issues.apache.org/jira/browse/IGNITE-3693
> Project: Ignite
> Issue Type: Bug
> Components: IGFS
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> Sample failure:
> http://149.202.210.143:8111/viewLog.html?buildId=299667=buildResultsDiv=IgniteTests_IgniteGgfs
> Stack trace:
> {code}
> java.lang.AssertionError: null
> at
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testFormat(IgfsAbstractSelfTest.java:1079)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1760)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1698)
> at java.lang.Thread.run(Thread.java:745)
> --- Stdout: ---
> [09:18:08,853][INFO ][main][root] >>> Starting test:
> IgfsLocalSecondaryFileSystemDualAsyncSelfTest#testFormat <<<
> [09:18:08,873][INFO ][main][root] >>> Stopping test:
> IgfsLocalSecondaryFileSystemDualAsyncSelfTest#testFormat in 19 ms <<<
> --- Stderr: ---
> [09:18:08,872][ERROR][main][root] Test failed.
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testFormat(IgfsAbstractSelfTest.java:1079)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1760)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1698)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3279) .NET: NLog integration
[
https://issues.apache.org/jira/browse/IGNITE-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova reassigned IGNITE-3279:
--
Assignee: Vasilisa Sidorova (was: Pavel Tupitsyn)
> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Vasilisa Sidorova
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3325) .NET: Improve CompiledQuery in LINQ provider
[
https://issues.apache.org/jira/browse/IGNITE-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432624#comment-15432624
]
ASF GitHub Bot commented on IGNITE-3325:
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/958
> .NET: Improve CompiledQuery in LINQ provider
>
>
> Key: IGNITE-3325
> URL: https://issues.apache.org/jira/browse/IGNITE-3325
> Project: Ignite
> Issue Type: Bug
> Components: community, platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net
> Fix For: 1.8
>
>
> User reported that the following code fails with "Error compiling query: all
> compiled query arguments should come from enclosing delegate parameters."
> {code}
> Func>> qry =
> CompiledQuery.Compile((int x, int y,int z) =>
> orderCache.AsCacheQueryable().Where(e => e.Value.OrderId % x == z).Take(y));
> {code}
> Other limitations are:
> * Embedded parameters are not supported
> * Maximum number of parameters is 8
> We should provide additional additional method to compile a delegate which
> takes an array of args.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3325) .NET: Improve CompiledQuery in LINQ provider
[
https://issues.apache.org/jira/browse/IGNITE-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432619#comment-15432619
]
Pavel Tupitsyn commented on IGNITE-3325:
There is a ticket to remove all deprecated code: IGNITE-3539
> .NET: Improve CompiledQuery in LINQ provider
>
>
> Key: IGNITE-3325
> URL: https://issues.apache.org/jira/browse/IGNITE-3325
> Project: Ignite
> Issue Type: Bug
> Components: community, platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net
> Fix For: 1.8
>
>
> User reported that the following code fails with "Error compiling query: all
> compiled query arguments should come from enclosing delegate parameters."
> {code}
> Func>> qry =
> CompiledQuery.Compile((int x, int y,int z) =>
> orderCache.AsCacheQueryable().Where(e => e.Value.OrderId % x == z).Take(y));
> {code}
> Other limitations are:
> * Embedded parameters are not supported
> * Maximum number of parameters is 8
> We should provide additional additional method to compile a delegate which
> takes an array of args.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3325) .NET: Improve CompiledQuery in LINQ provider
[
https://issues.apache.org/jira/browse/IGNITE-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432528#comment-15432528
]
Pavel Tupitsyn edited comment on IGNITE-3325 at 8/23/16 11:01 AM:
--
Pavel,
Fix is good to merge. Please go ahead. I would only ask you to create a ticket
to remove deprecation for 2.0.
was (Author: vozerov):
Pavel,
Fix is good to merge. Please go ahead. I would only ask you to create a ticket
to remove deprectaion for 2.0.
> .NET: Improve CompiledQuery in LINQ provider
>
>
> Key: IGNITE-3325
> URL: https://issues.apache.org/jira/browse/IGNITE-3325
> Project: Ignite
> Issue Type: Bug
> Components: community, platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net
> Fix For: 1.8
>
>
> User reported that the following code fails with "Error compiling query: all
> compiled query arguments should come from enclosing delegate parameters."
> {code}
> Func>> qry =
> CompiledQuery.Compile((int x, int y,int z) =>
> orderCache.AsCacheQueryable().Where(e => e.Value.OrderId % x == z).Take(y));
> {code}
> Other limitations are:
> * Embedded parameters are not supported
> * Maximum number of parameters is 8
> We should provide additional additional method to compile a delegate which
> takes an array of args.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3539) .NET: Remove deprecated code
[ https://issues.apache.org/jira/browse/IGNITE-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-3539: --- Description: Look for [Obsolete] attributes > .NET: Remove deprecated code > > > Key: IGNITE-3539 > URL: https://issues.apache.org/jira/browse/IGNITE-3539 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .net, breaking-api > Fix For: 2.0 > > > Look for [Obsolete] attributes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3279) .NET: NLog integration
[
https://issues.apache.org/jira/browse/IGNITE-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432611#comment-15432611
]
Pavel Tupitsyn edited comment on IGNITE-3279 at 8/23/16 10:56 AM:
--
How to test:
* Use `Ignite Platform .NET NuGet NEW` TeamCity suite on master branch to build
all NuGet packages. There should be `Apache.Ignite.NLog.*.nupkg` package in the
artifacts.
* Download all artifacts to an empty .
* Create a new console project in Visual Studio.
* In Visual Studio Package Manager Console run `Install-Package
Apache.Ignite.NLog -Pre -Source `.
* Run the following code and observe colored console output (instead of the
usual gray-only):
{code}
using System.Collections.Generic;
using Apache.Ignite.Core;
using Apache.Ignite.Core.Log;
using Apache.Ignite.NLog;
using NLog;
using NLog.Config;
using NLog.Targets;
using LogLevel = NLog.LogLevel;
namespace ConsoleApplication14
{
internal class Program
{
private static void Main(string[] args)
{
var logCfg = new LoggingConfiguration();
var target = new ColoredConsoleTarget();
logCfg.AddTarget("con", target);
logCfg.LoggingRules.Add(new LoggingRule("*", LogLevel.Info,
target));
LogManager.Configuration = logCfg;
var cfg = new IgniteConfiguration
{
Logger = new IgniteNLogLogger(),
JvmOptions = new [] {"-DIGNITE_QUIET=false"}
};
var ignite = Ignition.Start(cfg);
ignite.Logger.Error("Test error!");
}
}
}
{code}
was (Author: ptupitsyn):
How to test:
* Use `Ignite Platform .NET NuGet NEW` TeamCity suite on master branch to build
all NuGet packages. There should be `Apache.Ignite.NLog.*.nupkg` package in the
artifacts.
* Download all artifacts to an empty .
* Create a new console project in Visual Studio.
* In Visual Studio Package Manager Console run `Install-Package
Apache.Ignite.NLog -Pre -Source `.
* Run the following code and observe colored console output (instead of the
usual gray-only):
{code}
using System.Collections.Generic;
using Apache.Ignite.Core;
using Apache.Ignite.Core.Log;
using Apache.Ignite.NLog;
using NLog;
using NLog.Config;
using NLog.Targets;
using LogLevel = NLog.LogLevel;
namespace ConsoleApplication14
{
internal class Program
{
private static void Main(string[] args)
{
var logCfg = new LoggingConfiguration();
var target = new ColoredConsoleTarget();
logCfg.AddTarget("con", target);
logCfg.LoggingRules.Add(new LoggingRule("*", LogLevel.Info,
target));
LogManager.Configuration = logCfg;
var cfg = new IgniteConfiguration
{
Logger = new
IgniteNLogLogger(LogManager.GetCurrentClassLogger()),
JvmOptions = new List {"-DIGNITE_QUIET=false"}
};
var ignite = Ignition.Start(cfg);
ignite.Logger.Error("Test error!");
}
}
}
{code}
> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3279) .NET: NLog integration
[
https://issues.apache.org/jira/browse/IGNITE-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-3279.
Resolution: Fixed
> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3279) .NET: NLog integration
[
https://issues.apache.org/jira/browse/IGNITE-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432611#comment-15432611
]
Pavel Tupitsyn commented on IGNITE-3279:
How to test:
* Use `Ignite Platform .NET NuGet NEW` TeamCity suite on master branch to build
all NuGet packages. There should be `Apache.Ignite.NLog.*.nupkg` package in the
artifacts.
* Download all artifacts to an empty .
* Create a new console project in Visual Studio.
* In Visual Studio Package Manager Console run `Install-Package
Apache.Ignite.NLog -Pre -Source `.
* Run the following code and observe colored console output (instead of the
usual gray-only):
{code}
using System.Collections.Generic;
using Apache.Ignite.Core;
using Apache.Ignite.Core.Log;
using Apache.Ignite.NLog;
using NLog;
using NLog.Config;
using NLog.Targets;
using LogLevel = NLog.LogLevel;
namespace ConsoleApplication14
{
internal class Program
{
private static void Main(string[] args)
{
var logCfg = new LoggingConfiguration();
var target = new ColoredConsoleTarget();
logCfg.AddTarget("con", target);
logCfg.LoggingRules.Add(new LoggingRule("*", LogLevel.Info,
target));
LogManager.Configuration = logCfg;
var cfg = new IgniteConfiguration
{
Logger = new
IgniteNLogLogger(LogManager.GetCurrentClassLogger()),
JvmOptions = new List {"-DIGNITE_QUIET=false"}
};
var ignite = Ignition.Start(cfg);
ignite.Logger.Error("Test error!");
}
}
}
{code}
> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3279) .NET: NLog integration
[
https://issues.apache.org/jira/browse/IGNITE-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432585#comment-15432585
]
ASF GitHub Bot commented on IGNITE-3279:
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/963
> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3279) .NET: NLog integration
[
https://issues.apache.org/jira/browse/IGNITE-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432584#comment-15432584
]
Pavel Tupitsyn commented on IGNITE-3279:
Fixed, merged to master.
> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3167) Hadoop: restore external execution.
[ https://issues.apache.org/jira/browse/IGNITE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432580#comment-15432580 ] Vladimir Ozerov commented on IGNITE-3167: - IGNITE-404 should be taken in count. Please look through TODOs in code where "ignite-404" is mentioned. > Hadoop: restore external execution. > --- > > Key: IGNITE-3167 > URL: https://issues.apache.org/jira/browse/IGNITE-3167 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: roadmap > > Some time ago we decided to get rid external execution mode. It appears to be > a wrong decision. > Hadoop users rely on its process-per-job nature in lot's places. One of such > case could be observed in HiBench Bayes benchmark: > 1) Job creates something in the local file system through Hadoop FileSystem > API. > 2) Then it tries to get this data using regular java.io.FileReader and > relative paths. > This doesn't work in embedded mode because our LocalFileSystem wrapper > assigns different work dirs for jobs, but process-wide working directory is > always the same. As a result, aforementioned benchmark doesn't work in > Ignite, but work with standard Hadoop job tracker. > It seems that we must return external execution back. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3167) Hadoop: restore external execution.
[ https://issues.apache.org/jira/browse/IGNITE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-3167: Assignee: Taras Ledkov > Hadoop: restore external execution. > --- > > Key: IGNITE-3167 > URL: https://issues.apache.org/jira/browse/IGNITE-3167 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: roadmap > > Some time ago we decided to get rid external execution mode. It appears to be > a wrong decision. > Hadoop users rely on its process-per-job nature in lot's places. One of such > case could be observed in HiBench Bayes benchmark: > 1) Job creates something in the local file system through Hadoop FileSystem > API. > 2) Then it tries to get this data using regular java.io.FileReader and > relative paths. > This doesn't work in embedded mode because our LocalFileSystem wrapper > assigns different work dirs for jobs, but process-wide working directory is > always the same. As a result, aforementioned benchmark doesn't work in > Ignite, but work with standard Hadoop job tracker. > It seems that we must return external execution back. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3726) .NET: Remove summaries from NuSpec
Pavel Tupitsyn created IGNITE-3726: -- Summary: .NET: Remove summaries from NuSpec Key: IGNITE-3726 URL: https://issues.apache.org/jira/browse/IGNITE-3726 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Priority: Minor Fix For: 1.8 If no summary is used then all of the description is used. However what gets displayed is based on the size of the Manage Packages dialog, the size of characters used in the text, whether the row is selected and the Install button is showing, whether you are using Visual Studio 2015 or an older version. (http://stackoverflow.com/questions/33264005/what-is-max-length-of-summary-and-description) Therefore I think we can remove summary altogether to avoid duplicate text. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3670) IGFS: Local secondary: Add test for listPath() method called for symlink to directory
[ https://issues.apache.org/jira/browse/IGNITE-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432545#comment-15432545 ] Taras Ledkov commented on IGNITE-3670: -- [Tests results|http://149.202.210.143:8111/project.html?projectId=IgniteTests_IgniteTests=pull%2F975%2Fhead] > IGFS: Local secondary: Add test for listPath() method called for symlink to > directory > - > > Key: IGNITE-3670 > URL: https://issues.apache.org/jira/browse/IGNITE-3670 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 1.8 > > > 1. Create symlink under the *workDir* that is points to directory that is > placed outside *workDir*; > 2. Call listPaths() for the IGFS path that is mapped to the symlink. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3723) Web console staging: there are absent fields on Import model from DB dialog
[ https://issues.apache.org/jira/browse/IGNITE-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-3723: --- Assignee: Maxim Afanasiev (was: Pavel Konstantinov) > Web console staging: there are absent fields on Import model from DB dialog > --- > > Key: IGNITE-3723 > URL: https://issues.apache.org/jira/browse/IGNITE-3723 > Project: Ignite > Issue Type: Bug > Components: UI >Reporter: Pavel Konstantinov >Assignee: Maxim Afanasiev >Priority: Minor > Attachments: ig-3723.png > > > Please see attachment -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3725) Web console: Import model from DB: error with unchecking schemas
[ https://issues.apache.org/jira/browse/IGNITE-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-3725: --- Assignee: Maxim Afanasiev > Web console: Import model from DB: error with unchecking schemas > > > Key: IGNITE-3725 > URL: https://issues.apache.org/jira/browse/IGNITE-3725 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Maxim Afanasiev >Priority: Minor > > Try to import model from any DB (in my case it was a MySQL) > On 'select schema' step uncheck all schemas by clicking on 'Schema' checkbox. > Expected - all schemas should become unchecked. > Observed - only first schema was unchecked. All the others stayed marked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3723) Web console staging: there are absent fields on Import model from DB dialog
[ https://issues.apache.org/jira/browse/IGNITE-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-3723: --- Assignee: Pavel Konstantinov > Web console staging: there are absent fields on Import model from DB dialog > --- > > Key: IGNITE-3723 > URL: https://issues.apache.org/jira/browse/IGNITE-3723 > Project: Ignite > Issue Type: Bug > Components: UI >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: ig-3723.png > > > Please see attachment -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3724) Web console: generated cache doesn't link to the selected cluster in special case
[ https://issues.apache.org/jira/browse/IGNITE-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-3724: --- Assignee: Maxim Afanasiev > Web console: generated cache doesn't link to the selected cluster in special > case > - > > Key: IGNITE-3724 > URL: https://issues.apache.org/jira/browse/IGNITE-3724 > Project: Ignite > Issue Type: Bug > Components: UI >Reporter: Pavel Konstantinov >Assignee: Maxim Afanasiev >Priority: Minor > > # create 3 clusters > # import model from DB from table which doesn't contain primary key > # on 'Save' page choose 'Clear All' in clusters drop down and then choose any > one cluster > # Save > Observing - newly created caches were not linked with selected cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2726) Visor shows zero size for OFFHEAP_TIERED cache
[
https://issues.apache.org/jira/browse/IGNITE-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-2726:
---
Assignee: Alexey Kuznetsov (was: Pavel Konstantinov)
> Visor shows zero size for OFFHEAP_TIERED cache
> --
>
> Key: IGNITE-2726
> URL: https://issues.apache.org/jira/browse/IGNITE-2726
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: sprint-1
>Reporter: Valentin Kulichenko
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Labels: community, customer
> Fix For: 1.6
>
> Attachments: IGNITE_2726_Offheap_size_in_cache_information_.patch
>
>
> To reproduce:
> 1. Change cache memory mode in {{CachePutGetExample}} to {{OFFHEAP_TIERED}}.
> 2. Run the example.
> 3. Connect with Visor and run {{cache -a}} command. See result below - number
> of entries is zero. With {{ONHEAP_TIERED}} it shows the correct cache size.
> {noformat}
> visor> cache -a
> Time of the snapshot: 02/25/16, 13:10:44
> +==+
> | Name(@) |Mode | Nodes | Entries |Hits|
> Misses | Reads| Writes |
> +==+
> | CachePutGetExample(@c0) | PARTITIONED | 1 | min: 0| min: 40|
> min: 0| min: 40| min: 40|
> | | | | avg: 0.00 | avg: 40.00 |
> avg: 0.00 | avg: 40.00 | avg: 40.00 |
> | | | | max: 0| max: 40|
> max: 0| max: 40| max: 40|
> +--+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2726) Visor shows zero size for OFFHEAP_TIERED cache
[
https://issues.apache.org/jira/browse/IGNITE-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432524#comment-15432524
]
Pavel Konstantinov commented on IGNITE-2726:
Successfully tested in branch.
> Visor shows zero size for OFFHEAP_TIERED cache
> --
>
> Key: IGNITE-2726
> URL: https://issues.apache.org/jira/browse/IGNITE-2726
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: sprint-1
>Reporter: Valentin Kulichenko
>Assignee: Pavel Konstantinov
>Priority: Critical
> Labels: community, customer
> Fix For: 1.6
>
> Attachments: IGNITE_2726_Offheap_size_in_cache_information_.patch
>
>
> To reproduce:
> 1. Change cache memory mode in {{CachePutGetExample}} to {{OFFHEAP_TIERED}}.
> 2. Run the example.
> 3. Connect with Visor and run {{cache -a}} command. See result below - number
> of entries is zero. With {{ONHEAP_TIERED}} it shows the correct cache size.
> {noformat}
> visor> cache -a
> Time of the snapshot: 02/25/16, 13:10:44
> +==+
> | Name(@) |Mode | Nodes | Entries |Hits|
> Misses | Reads| Writes |
> +==+
> | CachePutGetExample(@c0) | PARTITIONED | 1 | min: 0| min: 40|
> min: 0| min: 40| min: 40|
> | | | | avg: 0.00 | avg: 40.00 |
> avg: 0.00 | avg: 40.00 | avg: 40.00 |
> | | | | max: 0| max: 40|
> max: 0| max: 40| max: 40|
> +--+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3627) ODBC: Tune ODBC capabilities to match capabilities of the Ignite SQL.
[
https://issues.apache.org/jira/browse/IGNITE-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432520#comment-15432520
]
Igor Sapego commented on IGNITE-3627:
-
Ok, then I'm going to add some tests while the work on IGNITE-3716 is in
progress.
> ODBC: Tune ODBC capabilities to match capabilities of the Ignite SQL.
> -
>
> Key: IGNITE-3627
> URL: https://issues.apache.org/jira/browse/IGNITE-3627
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Critical
> Labels: important, odbc
> Fix For: 1.8
>
>
> Capabilities provided by {{ConnectionInfo}} class should be adjusted so that
> {{SQLGetInfo}} would return real capabilities of Ignite SQL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3471) Do not send previous value to client node for invoke() when possible
[
https://issues.apache.org/jira/browse/IGNITE-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Velichko reassigned IGNITE-3471:
---
Assignee: Andrey Velichko
> Do not send previous value to client node for invoke() when possible
>
>
> Key: IGNITE-3471
> URL: https://issues.apache.org/jira/browse/IGNITE-3471
> Project: Ignite
> Issue Type: Task
> Components: cache
>Affects Versions: 1.4
>Reporter: Alexey Goncharuk
>Assignee: Andrey Velichko
>
> Currently for invoke() or invokeAll() methods we send previous cache value to
> near node and apply EntryProcessor locally to get a return value. This can
> induce a significant overhead when cache value is much larger than entry
> processor result.
> For many cases this can be avoided, e.g.
> {code}
> try (tx = txStart()) {
> cache.invoke(key, EP); // No need to send previous value to client in
> this case.
> tx.commit();
> }
> {code}
> Note that we need to add additional handling of such a case:
> {code}
> try (tx = txStart()) {
> cache.invoke(key, EP); // No need to send previous value to client in
> this case.
> cache.get(key); // This should actually get the current cache value from
> primary node and apply an entry processor locally to get the updated value.
> tx.commit();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3632) IGFS: Use task execution for PARTITIONED cache when metadata is co-located and current node is not affinity node.
[ https://issues.apache.org/jira/browse/IGNITE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432415#comment-15432415 ] Taras Ledkov commented on IGNITE-3632: -- [Tests results|http://149.202.210.143:8111/project.html?projectId=IgniteTests_IgniteTests=pull%2F969%2Fhead] > IGFS: Use task execution for PARTITIONED cache when metadata is co-located > and current node is not affinity node. > - > > Key: IGNITE-3632 > URL: https://issues.apache.org/jira/browse/IGNITE-3632 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov > Fix For: 1.8 > > > If the following conditions are valid: > 1) Metadata cache is PARTITIONED > 2) Metadata co-location is enabled > 3) Current node is not primary node > Then we should use client task execution because this situation is > indistinguishable from running IGFS method on a client node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3725) Web console: Import model from DB: error with unchecking schemas
Pavel Konstantinov created IGNITE-3725: -- Summary: Web console: Import model from DB: error with unchecking schemas Key: IGNITE-3725 URL: https://issues.apache.org/jira/browse/IGNITE-3725 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Priority: Minor Try to import model from any DB (in my case it was a MySQL) On 'select schema' step uncheck all schemas by clicking on 'Schema' checkbox. Expected - all schemas should become unchecked. Observed - only first schema was unchecked. All the others stayed marked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3724) Web console: generated cache doesn't link to the selected cluster in special case
Pavel Konstantinov created IGNITE-3724: -- Summary: Web console: generated cache doesn't link to the selected cluster in special case Key: IGNITE-3724 URL: https://issues.apache.org/jira/browse/IGNITE-3724 Project: Ignite Issue Type: Bug Components: UI Reporter: Pavel Konstantinov Priority: Minor # create 3 clusters # import model from DB from table which doesn't contain primary key # on 'Save' page choose 'Clear All' in clusters drop down and then choose any one cluster # Save Observing - newly created caches were not linked with selected cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3670) IGFS: Local secondary: Add test for listPath() method called for symlink to directory
[
https://issues.apache.org/jira/browse/IGNITE-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432390#comment-15432390
]
Taras Ledkov edited comment on IGNITE-3670 at 8/23/16 8:38 AM:
---
{panel:title=Vladimir}
determine the path to be a symlink, we call *dir.delete()*
which will fail if directory is not empty.
{panel}
Not true. If the *file* is symlink and *file.delete()* is called, then the
symlink is deleted.
I think it is a right and expected behavior. When the user creates symbolic
link to directory he doesn't expect delete target contents when symlink is
deleted recursive.
was (Author: tledkov-gridgain):
{panel:title=Vladimir}
determine the path to be a symlink, we call
{dir.delete()}
which will fail if directory is not empty.
{panel}
Not true. If the *file* is symlink and *file.delete()* is called, then the
symlink is deleted.
I think it is a right and expected behavior. When the user creates symbolic
link to directory he doesn't expect delete target contents when symlink is
deleted recursive.
> IGFS: Local secondary: Add test for listPath() method called for symlink to
> directory
> -
>
> Key: IGNITE-3670
> URL: https://issues.apache.org/jira/browse/IGNITE-3670
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> 1. Create symlink under the *workDir* that is points to directory that is
> placed outside *workDir*;
> 2. Call listPaths() for the IGFS path that is mapped to the symlink.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3670) IGFS: Local secondary: Add test for listPath() method called for symlink to directory
[
https://issues.apache.org/jira/browse/IGNITE-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432390#comment-15432390
]
Taras Ledkov edited comment on IGNITE-3670 at 8/23/16 8:38 AM:
---
{panel:title=Vladimir}
determine the path to be a symlink, we call
{dir.delete()}
which will fail if directory is not empty.
{panel}
Not true. If the *file* is symlink and *file.delete()* is called, then the
symlink is deleted.
I think it is a right and expected behavior. When the user creates symbolic
link to directory he doesn't expect delete target contents when symlink is
deleted recursive.
was (Author: tledkov-gridgain):
{panel:title=Vladimir}
determine the path to be a symlink, we call
{dir.delete()}
which will fail if directory is not empty.
{panel}
Not true. If the *file* is symlink and file.delete() is called, then the
symlink is deleted.
I think it is a right and expected behavior. When the user creates symbolic
link to directory he doesn't expect delete target contents when symlink is
deleted recursive.
> IGFS: Local secondary: Add test for listPath() method called for symlink to
> directory
> -
>
> Key: IGNITE-3670
> URL: https://issues.apache.org/jira/browse/IGNITE-3670
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> 1. Create symlink under the *workDir* that is points to directory that is
> placed outside *workDir*;
> 2. Call listPaths() for the IGFS path that is mapped to the symlink.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3670) IGFS: Local secondary: Add test for listPath() method called for symlink to directory
[
https://issues.apache.org/jira/browse/IGNITE-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432390#comment-15432390
]
Taras Ledkov commented on IGNITE-3670:
--
{panel:title=Vladimir}
determine the path to be a symlink, we call
{dir.delete()}
which will fail if directory is not empty.
{panel}
Not true. If the *file* is symlink and file.delete() is called, then the
symlink is deleted.
I think it is a right and expected behavior. When the user creates symbolic
link to directory he doesn't expect delete target contents when symlink is
deleted recursive.
> IGFS: Local secondary: Add test for listPath() method called for symlink to
> directory
> -
>
> Key: IGNITE-3670
> URL: https://issues.apache.org/jira/browse/IGNITE-3670
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> 1. Create symlink under the *workDir* that is points to directory that is
> placed outside *workDir*;
> 2. Call listPaths() for the IGFS path that is mapped to the symlink.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3723) Web console staging: there are absent fields on Import model from DB dialog
[ https://issues.apache.org/jira/browse/IGNITE-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-3723: --- Attachment: ig-3723.png > Web console staging: there are absent fields on Import model from DB dialog > --- > > Key: IGNITE-3723 > URL: https://issues.apache.org/jira/browse/IGNITE-3723 > Project: Ignite > Issue Type: Bug > Components: UI >Reporter: Pavel Konstantinov >Priority: Minor > Attachments: ig-3723.png > > > Please see attachment -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3723) Web console staging: there are absent fields on Import model from DB dialog
Pavel Konstantinov created IGNITE-3723: -- Summary: Web console staging: there are absent fields on Import model from DB dialog Key: IGNITE-3723 URL: https://issues.apache.org/jira/browse/IGNITE-3723 Project: Ignite Issue Type: Bug Components: UI Reporter: Pavel Konstantinov Priority: Minor Please see attachment -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2726) Visor shows zero size for OFFHEAP_TIERED cache
[
https://issues.apache.org/jira/browse/IGNITE-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko resolved IGNITE-2726.
---
Resolution: Fixed
Assignee: Pavel Konstantinov (was: Vasiliy Sisko)
> Visor shows zero size for OFFHEAP_TIERED cache
> --
>
> Key: IGNITE-2726
> URL: https://issues.apache.org/jira/browse/IGNITE-2726
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: sprint-1
>Reporter: Valentin Kulichenko
>Assignee: Pavel Konstantinov
>Priority: Critical
> Labels: community, customer
> Fix For: 1.6
>
> Attachments: IGNITE_2726_Offheap_size_in_cache_information_.patch
>
>
> To reproduce:
> 1. Change cache memory mode in {{CachePutGetExample}} to {{OFFHEAP_TIERED}}.
> 2. Run the example.
> 3. Connect with Visor and run {{cache -a}} command. See result below - number
> of entries is zero. With {{ONHEAP_TIERED}} it shows the correct cache size.
> {noformat}
> visor> cache -a
> Time of the snapshot: 02/25/16, 13:10:44
> +==+
> | Name(@) |Mode | Nodes | Entries |Hits|
> Misses | Reads| Writes |
> +==+
> | CachePutGetExample(@c0) | PARTITIONED | 1 | min: 0| min: 40|
> min: 0| min: 40| min: 40|
> | | | | avg: 0.00 | avg: 40.00 |
> avg: 0.00 | avg: 40.00 | avg: 40.00 |
> | | | | max: 0| max: 40|
> max: 0| max: 40| max: 40|
> +--+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2726) Visor shows zero size for OFFHEAP_TIERED cache
[
https://issues.apache.org/jira/browse/IGNITE-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432242#comment-15432242
]
Vasiliy Sisko commented on IGNITE-2726:
---
Implemented showing of detailed information for Per nodes table:
{noformat}
Nodes for: CachePutGetExample(@c0)
+==+
| Node ID8(@), IP | CPUs | Heap Used | CPU Load | Up Time|
Size| Hi/Mi/Rd/Wr |
+==+
| F5B72F53(@n1), 172.17.0.1 | 8| 1.08 %| 0.40 % | 02:25:36:380 |
Total: 9 | Hi: 0 |
| | | | | |
Heap: 0 | Mi: 0 |
| | | | | |
Off Heap: 9 | Rd: 0 |
| | | | | |
Off Heap Memory: 834b | Wr: 0 |
+---+--+---+--+--+---+-+
| 0556CD57(@n0), 172.17.0.1 | 8| 1.86 %| 1.43 % | 02:30:57:743 |
Total: 11 | Hi: 0 |
| | | | | |
Heap: 0 | Mi: 0 |
| | | | | |
Off Heap: 11| Rd: 0 |
| | | | | |
Off Heap Memory: 1,016b | Wr: 0 |
+--+
{noformat}
> Visor shows zero size for OFFHEAP_TIERED cache
> --
>
> Key: IGNITE-2726
> URL: https://issues.apache.org/jira/browse/IGNITE-2726
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: sprint-1
>Reporter: Valentin Kulichenko
>Assignee: Vasiliy Sisko
>Priority: Critical
> Labels: community, customer
> Fix For: 1.6
>
> Attachments: IGNITE_2726_Offheap_size_in_cache_information_.patch
>
>
> To reproduce:
> 1. Change cache memory mode in {{CachePutGetExample}} to {{OFFHEAP_TIERED}}.
> 2. Run the example.
> 3. Connect with Visor and run {{cache -a}} command. See result below - number
> of entries is zero. With {{ONHEAP_TIERED}} it shows the correct cache size.
> {noformat}
> visor> cache -a
> Time of the snapshot: 02/25/16, 13:10:44
> +==+
> | Name(@) |Mode | Nodes | Entries |Hits|
> Misses | Reads| Writes |
> +==+
> | CachePutGetExample(@c0) | PARTITIONED | 1 | min: 0| min: 40|
> min: 0| min: 40| min: 40|
> | | | | avg: 0.00 | avg: 40.00 |
> avg: 0.00 | avg: 40.00 | avg: 40.00 |
> | | | | max: 0| max: 40|
> max: 0| max: 40| max: 40|
> +--+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
