[jira] [Commented] (IGNITE-5174) Need to have opportunity to list only server nodes for specified topology version
[ https://issues.apache.org/jira/browse/IGNITE-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997861#comment-15997861 ] ASF GitHub Bot commented on IGNITE-5174: GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/1910 IGNITE-5174 client nodes filter func You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5174 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1910.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1910 commit 2185c173059db0615bfbb6b9d54ed92f5e1cb511 Author: Evgeny Stanilovskiy Date: 2017-05-05T06:50:04Z IGNITE-5174 client nodes filter func > Need to have opportunity to list only server nodes for specified topology > version > - > > Key: IGNITE-5174 > URL: https://issues.apache.org/jira/browse/IGNITE-5174 > Project: Ignite > Issue Type: Bug >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Minor > Fix For: 2.1 > > > Need to have common utility function which filters client nodes for specified > topology version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5174) Need to have opportunity to list only server nodes for specified topology version
Stanilovsky Evgeny created IGNITE-5174: -- Summary: Need to have opportunity to list only server nodes for specified topology version Key: IGNITE-5174 URL: https://issues.apache.org/jira/browse/IGNITE-5174 Project: Ignite Issue Type: Bug Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny Priority: Minor Fix For: 2.1 Need to have common utility function which filters client nodes for specified topology version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5037) Fix broken @AffinityKeyMapped annotation for compute jobs.
[ https://issues.apache.org/jira/browse/IGNITE-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5037: --- Description: See related discussion on dev list entitled Proper collocation of computations and data (http://apache-ignite-developers.2346864.n4.nabble.com/Proper-collocation-of-computations-and-data-td16945.html). We must repair data affinity routing for compute jobs. It should work same as for affinityCall/Run with partition. was: See related discussion on dev list entitled Proper collocation of computations and data. We must repair data affinity routing for compute jobs. It should work same as for affinityCall/Run with partition. > Fix broken @AffinityKeyMapped annotation for compute jobs. > -- > > Key: IGNITE-5037 > URL: https://issues.apache.org/jira/browse/IGNITE-5037 > Project: Ignite > Issue Type: Improvement >Affects Versions: 1.7 >Reporter: Alexei Scherbakov > Labels: newbie > Fix For: 2.1 > > > See related discussion on dev list entitled Proper collocation of > computations and data > (http://apache-ignite-developers.2346864.n4.nabble.com/Proper-collocation-of-computations-and-data-td16945.html). > We must repair data affinity routing for compute jobs. It should work same as > for affinityCall/Run with partition. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5173) Write-Behind store flushes single entry at a time in the sync mode
[
https://issues.apache.org/jira/browse/IGNITE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-5173:
Description:
When the write-behind store reaches maximum write-behind queue/buffer size on
the next update operation, then the data will be flushed from the queue
synchronously in order to free some room for the just arrived update. The issue
is that the store flushes a single entry at a time in the synchronous mode that
can dramatically affect the performance.
The following has to be addressed as a part of the ticket:
* the store has to flush multiple entries in the sync mode to avoid a
performance hit.
* {{CacheConfiguration.getWriteBehindFlushSize}} and respective setter method
must be renamed to {{CacheConfiguration.getWriteBehindBufferSize}}. Presently
it's totally confusing.
See more details here:
http://apache-ignite-users.70518.x6.nabble.com/CacheStore-s-Performance-Drops-Dramatically-Why-td12337.html
was:
When the write-behind store reaches maximum write-behind queue/buffer size on
the next update operation, then the data will be flushed from the queue
synchronously in order to free some room for the just arrived update. The issue
is that the store flushes a single entry at a time in the synchronous mode that
can dramatically affect the performance.
The following has to be addressed as a part of the ticket:
* the store has to flush multiple entries in the sync mode to avoid a
performance hit.
* `CacheConfiguration.getWriteBehindFlushSize` and respective setter method
must be renamed to `CacheConfiguration.getWriteBehindBufferSize`. Presently
it's totally confusing.
See more details here:
http://apache-ignite-users.70518.x6.nabble.com/CacheStore-s-Performance-Drops-Dramatically-Why-td12337.html
> Write-Behind store flushes single entry at a time in the sync mode
> --
>
> Key: IGNITE-5173
> URL: https://issues.apache.org/jira/browse/IGNITE-5173
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
> Fix For: 2.1
>
>
> When the write-behind store reaches maximum write-behind queue/buffer size on
> the next update operation, then the data will be flushed from the queue
> synchronously in order to free some room for the just arrived update. The
> issue is that the store flushes a single entry at a time in the synchronous
> mode that can dramatically affect the performance.
> The following has to be addressed as a part of the ticket:
> * the store has to flush multiple entries in the sync mode to avoid a
> performance hit.
> * {{CacheConfiguration.getWriteBehindFlushSize}} and respective setter method
> must be renamed to {{CacheConfiguration.getWriteBehindBufferSize}}. Presently
> it's totally confusing.
> See more details here:
> http://apache-ignite-users.70518.x6.nabble.com/CacheStore-s-Performance-Drops-Dramatically-Why-td12337.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5173) Write-Behind store flushes single entry at a time in the sync mode
Denis Magda created IGNITE-5173: --- Summary: Write-Behind store flushes single entry at a time in the sync mode Key: IGNITE-5173 URL: https://issues.apache.org/jira/browse/IGNITE-5173 Project: Ignite Issue Type: Bug Reporter: Denis Magda Fix For: 2.1 When the write-behind store reaches maximum write-behind queue/buffer size on the next update operation, then the data will be flushed from the queue synchronously in order to free some room for the just arrived update. The issue is that the store flushes a single entry at a time in the synchronous mode that can dramatically affect the performance. The following has to be addressed as a part of the ticket: * the store has to flush multiple entries in the sync mode to avoid a performance hit. * `CacheConfiguration.getWriteBehindFlushSize` and respective setter method must be renamed to `CacheConfiguration.getWriteBehindBufferSize`. Presently it's totally confusing. See more details here: http://apache-ignite-users.70518.x6.nabble.com/CacheStore-s-Performance-Drops-Dramatically-Why-td12337.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5172) .NET: Dynamic type registration uses assembly-qualified type name
[
https://issues.apache.org/jira/browse/IGNITE-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997291#comment-15997291
]
ASF GitHub Bot commented on IGNITE-5172:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/1909
IGNITE-5172 .NET: Fix type name resolving during dynamic registration
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-5172
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1909.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1909
commit 190476e55d29214d8c5dd87523e70abb58175efa
Author: Pavel Tupitsyn
Date: 2017-05-04T18:07:35Z
IGNITE-5172 .NET: Fix type name mapping for dynamic registration
commit 95e0c20285c8b84307753b09eff5c8aea8efde95
Author: Pavel Tupitsyn
Date: 2017-05-04T18:48:26Z
Add test
commit 7fefe5f60a505b85e0d03576de18bc70e52ec677
Author: Pavel Tupitsyn
Date: 2017-05-04T18:50:31Z
Fix compilation
commit 435a91a3258615e0e4fc1a1e23dab96687ddb1f0
Author: Pavel Tupitsyn
Date: 2017-05-04T19:13:02Z
Fixing TypeResolver
commit 31435b3ae30d7326c5ec726c3806e9074b1d02ee
Author: Pavel Tupitsyn
Date: 2017-05-04T19:23:51Z
Fixing generic type resolver
> .NET: Dynamic type registration uses assembly-qualified type name
> -
>
> Key: IGNITE-5172
> URL: https://issues.apache.org/jira/browse/IGNITE-5172
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> {{BinaryProcessor.RegisterType}} uses {{AssemblyQualifiedName}}, which
> includes assembly version.
> This has two issues:
> * We ignore current name mapper, so this type name is not the same as type
> name in binary metadata, marshaller, etc
> * This breaks when same type comes from assemblies with different versions,
> which is a valid scenario. Binary protocol is flexible and does not care
> about type versions, it tolerates new or missing fields.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5038) BinaryMarshaller might need to use context class loader for deserialization
[ https://issues.apache.org/jira/browse/IGNITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-5038: Description: There is a special use case discussed on the dev list: http://apache-ignite-developers.2346864.n4.nabble.com/Re-BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-td17126.html#a17224 According to the use case, BinaryMarshaller might need to try to deserialize an object using a context class loader if it failed to do so with a custom classloader (`IgniteConfiguration.getClassLoader()`) or the system one. was: In case if used custom class loader object could be serialized to BinaryObject, but de-serialization will fail with ClassNotFoundException. There should be possibility to explicitly set ClassLoader on object de-serialization: BinaryObject.deserialize(ClassLoader) > BinaryMarshaller might need to use context class loader for deserialization > --- > > Key: IGNITE-5038 > URL: https://issues.apache.org/jira/browse/IGNITE-5038 > Project: Ignite > Issue Type: New Feature > Components: cache >Affects Versions: 2.0 >Reporter: Dmitry Karachentsev > Labels: features > Fix For: 2.1 > > > There is a special use case discussed on the dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/Re-BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-td17126.html#a17224 > According to the use case, BinaryMarshaller might need to try to deserialize > an object using a context class loader if it failed to do so with a custom > classloader (`IgniteConfiguration.getClassLoader()`) or the system one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5038) BinaryMarshaller might need to use context class loader for deserialization
[ https://issues.apache.org/jira/browse/IGNITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-5038: Summary: BinaryMarshaller might need to use context class loader for deserialization (was: Add BinaryObject.deserialize(ClassLoader) method) > BinaryMarshaller might need to use context class loader for deserialization > --- > > Key: IGNITE-5038 > URL: https://issues.apache.org/jira/browse/IGNITE-5038 > Project: Ignite > Issue Type: New Feature > Components: cache >Affects Versions: 2.0 >Reporter: Dmitry Karachentsev > Labels: features > Fix For: 2.1 > > > In case if used custom class loader object could be serialized to > BinaryObject, but de-serialization will fail with ClassNotFoundException. > There should be possibility to explicitly set ClassLoader on object > de-serialization: > BinaryObject.deserialize(ClassLoader) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4976) Document C++ Continuous Queries Remote Filters
[ https://issues.apache.org/jira/browse/IGNITE-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-4976: --- Assignee: Prachi Garg (was: Denis Magda) > Document C++ Continuous Queries Remote Filters > -- > > Key: IGNITE-4976 > URL: https://issues.apache.org/jira/browse/IGNITE-4976 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 1.9 >Reporter: Denis Magda >Assignee: Prachi Garg > Labels: cpp, documentation > Fix For: 2.1 > > > [~isapego], please document CQ remote filters feature (IGNITE-3575) and > assign the ticket on me and Prachi for the final modifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4976) Document C++ Continuous Queries Remote Filters
[ https://issues.apache.org/jira/browse/IGNITE-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997268#comment-15997268 ] Denis Magda commented on IGNITE-4976: - [~isapego], thanks. Frankly, it's better to split this single block with the code into four different pieces and move them out across the doc. Did this: https://apacheignite-cpp.readme.io/docs/continuous-queries [~pgarg], please do the final review and close the ticket. > Document C++ Continuous Queries Remote Filters > -- > > Key: IGNITE-4976 > URL: https://issues.apache.org/jira/browse/IGNITE-4976 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 1.9 >Reporter: Denis Magda >Assignee: Denis Magda > Labels: cpp, documentation > Fix For: 2.1 > > > [~isapego], please document CQ remote filters feature (IGNITE-3575) and > assign the ticket on me and Prachi for the final modifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4926) .NET: Join fails in LINQ when subquery is using Select clause
[
https://issues.apache.org/jira/browse/IGNITE-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Stronchinskiy reassigned IGNITE-4926:
Assignee: Sergey Stronchinskiy
> .NET: Join fails in LINQ when subquery is using Select clause
> -
>
> Key: IGNITE-4926
> URL: https://issues.apache.org/jira/browse/IGNITE-4926
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Sergey Stronchinskiy
>Assignee: Sergey Stronchinskiy
>Priority: Minor
> Labels: .NET, LINQ
> Fix For: 2.1
>
>
> Using {{Join}} with subquery works when subquery does not contain {{Select}}
> clause:
> {code}
> var persons = GetPersonCache().AsCacheQueryable().Where(x => x.Key >= 0);
> var orgs = GetOrgCache().AsCacheQueryable().Where(x => x.Key > 10);
> var res = persons.Join(orgs,
> p => p.Value.OrganizationId,
> o => o.Value.Id, (p, o) => p)
> .Where(x => x.Key >= 0)
> .ToList();
> {code}
> And fails when subquery is using {{Select}}:
> {code}
> var res = persons
> .Join(
> orgs.Where(orgEntry => orgEntry.Value.Name == "Org_1")
> .Select(orgEntry => orgEntry.Key),
> e => e.Value.OrganizationId,
> i => i,
> (e, i) => e)
> .ToList();
> {code}
> Exception:
> {code}
> Failed to parse SQL query: select _T0._key, _T0._val from "".Person as _T0
> inner join (select _T1._key from "".Organization as _T1 where (_T1._key > ?)
> and (_T1.Name = ?) ) as _T2 on (_T2._key, _T2._val = _T0.OrganizationId)
> where (_T0._key >= ?)
> Caused by: org.h2.jdbc.JdbcSQLException: Column "_T2._VAL" not found;
> {code}
> This can be reproduced in {{CacheLinqTest.TestSubqueryJoin}} by adding next:
> {code}
> var foo = persons
> .Join(
> orgs.Where(orgEntry => orgEntry.Value.Name == "Org_1")
> .Select(orgEntry => orgEntry.Key),
> e => e.Value.OrganizationId,
> i => i,
> (e, i) => e)
> .ToArray();
> {code}
> or
> {code}
> var foo = orgs
> .Where(orgEntry => orgEntry.Value.Name == "Org_1")
> .Select(orgEntry => orgEntry.Key);
> var bar = persons
> .Join(foo, e => e.Value.OrganizationId, i => i, (e, i) => e)
> .ToArray();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5172) .NET: Dynamic type registration uses assembly-qualified type name
[
https://issues.apache.org/jira/browse/IGNITE-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-5172:
---
Fix Version/s: (was: 2.0)
2.1
> .NET: Dynamic type registration uses assembly-qualified type name
> -
>
> Key: IGNITE-5172
> URL: https://issues.apache.org/jira/browse/IGNITE-5172
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> {{BinaryProcessor.RegisterType}} uses {{AssemblyQualifiedName}}, which
> includes assembly version.
> This has two issues:
> * We ignore current name mapper, so this type name is not the same as type
> name in binary metadata, marshaller, etc
> * This breaks when same type comes from assemblies with different versions,
> which is a valid scenario. Binary protocol is flexible and does not care
> about type versions, it tolerates new or missing fields.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5172) .NET: Dynamic type registration uses assembly-qualified type name
Pavel Tupitsyn created IGNITE-5172:
--
Summary: .NET: Dynamic type registration uses assembly-qualified
type name
Key: IGNITE-5172
URL: https://issues.apache.org/jira/browse/IGNITE-5172
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.0
{{BinaryProcessor.RegisterType}} uses {{AssemblyQualifiedName}}, which includes
assembly version.
This has two issues:
* We ignore current name mapper, so this type name is not the same as type name
in binary metadata, marshaller, etc
* This breaks when same type comes from assemblies with different versions,
which is a valid scenario. Binary protocol is flexible and does not care about
type versions, it tolerates new or missing fields.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5171) Show how to make index fields of embedded objects
Denis Magda created IGNITE-5171:
---
Summary: Show how to make index fields of embedded objects
Key: IGNITE-5171
URL: https://issues.apache.org/jira/browse/IGNITE-5171
Project: Ignite
Issue Type: Sub-task
Reporter: Denis Magda
Assignee: Denis Magda
Fix For: 2.1
Document and demonstrate how to index and use fields of embedded objects:
https://apacheignite.readme.io/v2.0/docs/indexes
For instance, if we have this object
Person {
int age;
int id;
Addrees addr;
}
where Address includes {street and zip} fileds.
Show how to index {{street}} and {{zip}} and use from SQL.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5171) Show how to index fields of embedded objects
[
https://issues.apache.org/jira/browse/IGNITE-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-5171:
Summary: Show how to index fields of embedded objects (was: Show how to
make index fields of embedded objects)
> Show how to index fields of embedded objects
>
>
> Key: IGNITE-5171
> URL: https://issues.apache.org/jira/browse/IGNITE-5171
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.1
>
>
> Document and demonstrate how to index and use fields of embedded objects:
> https://apacheignite.readme.io/v2.0/docs/indexes
> For instance, if we have this object
> Person {
> int age;
> int id;
> Addrees addr;
> }
> where Address includes {street and zip} fileds.
> Show how to index {{street}} and {{zip}} and use from SQL.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-2492) .NET: Peer assembly loading
[ https://issues.apache.org/jira/browse/IGNITE-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996988#comment-15996988 ] Pavel Tupitsyn commented on IGNITE-2492: [~vozerov] what do you think, should we enable peer loading by default? I understand that this is often not recommended for production usage, and it is false in Java. But we can say the same about default Multicast IP finder. It is default because it does not require any setup from the user. So I think having peer deployment enabled by default will simplify life for new users - POCs, demos, examples, and so on. > .NET: Peer assembly loading > --- > > Key: IGNITE-2492 > URL: https://issues.apache.org/jira/browse/IGNITE-2492 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net > Fix For: 2.1 > > > Similar to peer class loading in Java, we can provide a possibility to load > assemblies on already started nodes, so that a node can execute jobs that are > not present on other nodes. > Considerations: > * Can we unload assemblies after use to free memory? This requires a separate > AppDomain, can we work with that? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5168) Make IGFS metrics available for user
[ https://issues.apache.org/jira/browse/IGNITE-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky updated IGNITE-5168: Description: Now in Ignite the only way to see IGFS metrics is to get them programmically from the code. But customers need them to understand what is cached in IGFS, so to expose the metrics would be useful. There are options to expose the metrics via 1) MBean 2) console Visor . 3) web console ( https://apacheignite-tools.readme.io/docs/ignite-web-console ) was: Now in Ignite the only way to see IGFS metrics is to get them programmically from the code. But customers need them to understand what is cached in IGFS, so to expose the metrics would be useful. There are options to expose the metrics via MBean and/or via console Visor interface. > Make IGFS metrics available for user > > > Key: IGNITE-5168 > URL: https://issues.apache.org/jira/browse/IGNITE-5168 > Project: Ignite > Issue Type: New Feature > Components: IGFS >Affects Versions: 2.0 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > > Now in Ignite the only way to see IGFS metrics is to get them programmically > from the code. But customers need them to understand what is cached in IGFS, > so to expose the metrics would be useful. > There are options to expose the metrics via > 1) MBean > 2) console Visor . > 3) web console ( https://apacheignite-tools.readme.io/docs/ignite-web-console > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5168) Make IGFS metrics available for user
[ https://issues.apache.org/jira/browse/IGNITE-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky updated IGNITE-5168: Summary: Make IGFS metrics available for user (was: Expose IGFS metrics via an MBean or console Visor.) > Make IGFS metrics available for user > > > Key: IGNITE-5168 > URL: https://issues.apache.org/jira/browse/IGNITE-5168 > Project: Ignite > Issue Type: New Feature > Components: IGFS >Affects Versions: 2.0 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > > Now in Ignite the only way to see IGFS metrics is to get them programmically > from the code. But customers need them to understand what is cached in IGFS, > so to expose the metrics would be useful. > There are options to expose the metrics via MBean and/or via console Visor > interface. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-3939) Compact long zero values binary representation
[ https://issues.apache.org/jira/browse/IGNITE-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996969#comment-15996969 ] ASF GitHub Bot commented on IGNITE-3939: Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1090 > Compact long zero values binary representation > -- > > Key: IGNITE-3939 > URL: https://issues.apache.org/jira/browse/IGNITE-3939 > Project: Ignite > Issue Type: Improvement > Components: binary >Affects Versions: 1.7 >Reporter: Andrew Mashenkov >Assignee: Taras Ledkov > Labels: important, performance > Fix For: 2.1 > > > We can use separate type for Long zero values and exclude 8-byte value from > binary representation. This will reduce memory footprint and network load. > Compatibility with previous versions MUST be preserved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-518) TTL is not updated for reader when entry is accessed on backup
[
https://issues.apache.org/jira/browse/IGNITE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996967#comment-15996967
]
ASF GitHub Bot commented on IGNITE-518:
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1636
> TTL is not updated for reader when entry is accessed on backup
> --
>
> Key: IGNITE-518
> URL: https://issues.apache.org/jira/browse/IGNITE-518
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-2
>Reporter: Alexey Goncharuk
>Assignee: Andrew Mashenkov
> Labels: Muted_test
> Fix For: 2.0
>
>
> When ttl is updated, readers are recorded locally and update is then sent
> based on collected data. When get is performed on backup, readers are empty,
> so near readers are not updated.
> {{IgniteCacheAtomicExpiryPolicyTest.testNearAccess}} fails.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (IGNITE-5071) Web Console: Support custom table names on model import
[ https://issues.apache.org/jira/browse/IGNITE-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov closed IGNITE-5071. -- Assignee: Alexey Kuznetsov (was: Andrey Novikov) > Web Console: Support custom table names on model import > --- > > Key: IGNITE-5071 > URL: https://issues.apache.org/jira/browse/IGNITE-5071 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 1.9 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 2.1 > > > We need to support table aliases aka custom table name on models import from > RDBMS. > See QueryEntity.TableName property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5170) .NET: Use peer deployment in examples
Pavel Tupitsyn created IGNITE-5170:
--
Summary: .NET: Use peer deployment in examples
Key: IGNITE-5170
URL: https://issues.apache.org/jira/browse/IGNITE-5170
Project: Ignite
Issue Type: Improvement
Components: platforms
Affects Versions: 2.1
Reporter: Pavel Tupitsyn
Fix For: 2.1
Once IGNITE-2492 is finished, we should simplify examples:
* Remove the requirement to start Apache.Ignite.exe with {{-assembly}} parameter
* Remove ExamplesDll project, put all classes into one project to avoid
confusion
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5169) ODBC: Rework handshake to allow different handlers
[ https://issues.apache.org/jira/browse/IGNITE-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996919#comment-15996919 ] Igor Sapego commented on IGNITE-5169: - [~vozerov] looks perfectly reasonable to me. I'll let you know once C++ part is ready. > ODBC: Rework handshake to allow different handlers > -- > > Key: IGNITE-5169 > URL: https://issues.apache.org/jira/browse/IGNITE-5169 > Project: Ignite > Issue Type: Task > Components: jdbc-driver, odbc, SQL >Reporter: Vladimir Ozerov >Assignee: Igor Sapego > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5169) ODBC: Rework handshake to allow different handlers
[ https://issues.apache.org/jira/browse/IGNITE-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996858#comment-15996858 ] Vladimir Ozerov commented on IGNITE-5169: - [~isapego], could you please review my changes. If you find them valid, let's change ODBC part accordingly. > ODBC: Rework handshake to allow different handlers > -- > > Key: IGNITE-5169 > URL: https://issues.apache.org/jira/browse/IGNITE-5169 > Project: Ignite > Issue Type: Task > Components: jdbc-driver, odbc, SQL >Reporter: Vladimir Ozerov >Assignee: Igor Sapego > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5169) ODBC: Rework handshake to allow different handlers
[
https://issues.apache.org/jira/browse/IGNITE-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996853#comment-15996853
]
Vladimir Ozerov commented on IGNITE-5169:
-
Request format:
1. {{BYTE}} - command (must be {{HANDSHAKE}})
2. {{SHORT}} - major version
3. {{SHORT}} - minor version
4. {{SHORT}} - maintenance version
5. Version-specific payload (see {{OdbcNioListener.prepareContext}})
Response format:
1. {{BOOLEAN}} - success flag, then if failed:
2. {{SHORT}} - node's protocol major version
3. {{SHORT}} - node's protocol minor version
4. {{SHORT}} - node's protocol maintenance version
5. {{STRING}} - optional error message
In case of non-success result client should either throw an exception or re-try
handshake with downgraded version (and payload)
> ODBC: Rework handshake to allow different handlers
> --
>
> Key: IGNITE-5169
> URL: https://issues.apache.org/jira/browse/IGNITE-5169
> Project: Ignite
> Issue Type: Task
> Components: jdbc-driver, odbc, SQL
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
> Fix For: 2.1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5169) ODBC: Rework handshake to allow different handlers
[ https://issues.apache.org/jira/browse/IGNITE-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996838#comment-15996838 ] ASF GitHub Bot commented on IGNITE-5169: GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1908 IGNITE-5169 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5169 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1908.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1908 commit 24a197c93c2abee65c2e362c806d1dfb4b398a2b Author: devozerov Date: 2017-05-04T14:49:03Z Finished Java part. > ODBC: Rework handshake to allow different handlers > -- > > Key: IGNITE-5169 > URL: https://issues.apache.org/jira/browse/IGNITE-5169 > Project: Ignite > Issue Type: Task > Components: jdbc-driver, odbc, SQL >Reporter: Vladimir Ozerov >Assignee: Igor Sapego > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5169) ODBC: Rework handshake to allow different handlers
Vladimir Ozerov created IGNITE-5169: --- Summary: ODBC: Rework handshake to allow different handlers Key: IGNITE-5169 URL: https://issues.apache.org/jira/browse/IGNITE-5169 Project: Ignite Issue Type: Task Components: jdbc-driver, odbc, SQL Reporter: Vladimir Ozerov Assignee: Igor Sapego Fix For: 2.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4939) Receive event before cache initialized
[
https://issues.apache.org/jira/browse/IGNITE-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996826#comment-15996826
]
Evgenii Zhuravlev commented on IGNITE-4939:
---
GridContiniousProcessor.onStart invokes
ctx.service().onContinuousProcessorStarted(ctx) too early, when caches not
create yet(it happens in GridCacheProcessor.onKernalStart).
It's not possible to move ctx.service().onContinuousProcessorStarted(ctx)
invoke to code after all caches start, because at the moment, when
discoveryManager starts, this method must be already invoked.
> Receive event before cache initialized
> --
>
> Key: IGNITE-4939
> URL: https://issues.apache.org/jira/browse/IGNITE-4939
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.9
>Reporter: Nikolay Tikhonov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.1
>
>
> Receive event before cache initialized that leads to the following:
> {noformat}
> Exception in thread "sys-#755%Default%" java.lang.IllegalArgumentException:
> Cache is not configured: ignite-sys-cache
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:3343)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.handleEvent(CacheContinuousQueryHandler.java:719)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:691)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:650)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:1086)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$2000(GridContinuousProcessor.java:97)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:741)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:102)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2332)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1042)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1900(GridIoManager.java:102)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:1011)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (IGNITE-5118) Table with name Object lead to compilation error in code generated by webconsole
[ https://issues.apache.org/jira/browse/IGNITE-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov closed IGNITE-5118. -- Assignee: Alexey Kuznetsov (was: Andrey Novikov) > Table with name Object lead to compilation error in code generated by > webconsole > > > Key: IGNITE-5118 > URL: https://issues.apache.org/jira/browse/IGNITE-5118 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.7 >Reporter: Evgenii Zhuravlev >Assignee: Alexey Kuznetsov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (IGNITE-4220) Allow to pass statements instead of strings to CacheStore.loadCache() implementations
[
https://issues.apache.org/jira/browse/IGNITE-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-4220:
-
Comment: was deleted
(was: [~amkad]
Fix for Cassandra store is more important than for POJO store.
If there is some issues with POJO unresolved yet, please make a PR for
Cassandra only so we can merge it tomorrow morning.)
> Allow to pass statements instead of strings to CacheStore.loadCache()
> implementations
> -
>
> Key: IGNITE-4220
> URL: https://issues.apache.org/jira/browse/IGNITE-4220
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Alexei Kaigorodov
> Fix For: 2.1
>
>
> Currently both Cassandra store and POJO store allow user to provide a set of
> queries used for data loading. However, there are cases when user may want to
> provide a {{Statement}} instead (e.g., prepared statements with parameter
> binding are used). We should support {{Statement}} arguments in store
> implementations as well as strings.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4842) IgniteCache.containsKey() may return false if entry is not in local backup yet on atomic cache
[ https://issues.apache.org/jira/browse/IGNITE-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996744#comment-15996744 ] Semen Boikov commented on IGNITE-4842: -- Hi, Reviewed changes, fix looks ok but you did not include test in the suite. Also I did not understand why test you added extends IgniteCacheContainsKeyAbstractSelfTest, I think it should extend GridCacheAbstractSelfTest, please fix this. Thanks > IgniteCache.containsKey() may return false if entry is not in local backup > yet on atomic cache > -- > > Key: IGNITE-4842 > URL: https://issues.apache.org/jira/browse/IGNITE-4842 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.9 >Reporter: Dmitry Karachentsev >Assignee: Dmitry Karachentsev > Fix For: 2.1 > > > Reproducer is in [PR#1641|https://github.com/apache/ignite/pull/1641] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4455) Node restarts may hang grid on exchange process
[ https://issues.apache.org/jira/browse/IGNITE-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev reassigned IGNITE-4455: - Assignee: Evgenii Zhuravlev > Node restarts may hang grid on exchange process > --- > > Key: IGNITE-4455 > URL: https://issues.apache.org/jira/browse/IGNITE-4455 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.8 >Reporter: Dmitry Karachentsev >Assignee: Evgenii Zhuravlev > > Node connect or disconnect may force grid hang on exchange process. > Refer test that reproduces problem: > [PR#1360|https://github.com/apache/ignite/pull/1360] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5084) PagesList.put() assertion: pageId != tailId
[
https://issues.apache.org/jira/browse/IGNITE-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh reassigned IGNITE-5084:
Assignee: Ilya Lantukh
> PagesList.put() assertion: pageId != tailId
> ---
>
> Key: IGNITE-5084
> URL: https://issues.apache.org/jira/browse/IGNITE-5084
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.0
>Reporter: Alexandr Kuramshin
>Assignee: Ilya Lantukh
>
> Get an error upon rebalancing on topology update
> {noformat}
> Failed processing message [senderId=78a8f841-5d40-4ac7-b26b-f1b5e7f3faa0,
> msg=GridDhtPartitionSupplyMessageV2 [updateSeq=142,
> topVer=AffinityTopologyVersion [topVer=8, minorTopVer=0], missed=null,
> clean=[0, 1, 2, 3, 4, 5, 6, 7, 8, 11, 12, 13, 14, 17, 19, 21, 20, 23, 22, 24,
> 26, 29, 28, 31, 35, 32, 33, 39, 36, 37, 42, 43, 40, 41, 44, 45, 51, 48, 55,
> 54, 53, 52, 58, 56, 63, 62, 60, 68, 69, 65, 66, 76, 77, 78, 74, 85, 87, 86,
> 81, 80, 82, 92, 91, 90, 98, 96, 97], msgSize=0, size=67, parts=[0, 1, 2, 3,
> 4, 5, 6, 7, 8, 11, 12, 13, 14, 17, 19, 21, 20, 23, 22, 24, 26, 29, 28, 31,
> 35, 32, 33, 39, 36, 37, 42, 43, 40, 41, 44, 45, 51, 48, 55, 54, 53, 52, 58,
> 56, 63, 62, 60, 68, 69, 65, 66, 76, 77, 78, 74, 85, 87, 86, 81, 80, 82, 92,
> 91, 90, 98, 96, 97], super=GridCacheMessage [msgId=100460, depInfo=null,
> err=null, skipPrepare=false, cacheId=-2100569601, cacheId=-2100569601]]]
> java.lang.AssertionError: pageId = 0, tailId = 281556581089286
> at
> org.apache.ignite.internal.processors.cache.database.freelist.PagesList.put(PagesList.java:~)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5167) ODBC: Abstract out handler and parser interfaces
[ https://issues.apache.org/jira/browse/IGNITE-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996640#comment-15996640 ] ASF GitHub Bot commented on IGNITE-5167: Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1907 > ODBC: Abstract out handler and parser interfaces > > > Key: IGNITE-5167 > URL: https://issues.apache.org/jira/browse/IGNITE-5167 > Project: Ignite > Issue Type: Task > Components: jdbc-driver, odbc, SQL >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 2.1 > > > This is necessary for smooth thin JDBC driver integrration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4501) Improvement of connection in a cluster of new node
[
https://issues.apache.org/jira/browse/IGNITE-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992726#comment-15992726
]
Alexander Menshikov edited comment on IGNITE-4501 at 5/4/17 12:25 PM:
--
[~yzhdanov]
Yakov, I has fixed this problem too, but fount new one. In the
GridDhtPartitionTopologyImpl#partitionMap(boolean onlyActive) I get an
assertion because node2part.valid() is false. I spent a week in trying to
understand what does it mean and how it connected with the discovery ring, but
failed.
was (Author: sharpler):
[~yzhdanov]
Yakov, I has fixed this problem too, but fount new one. In the
GridDhtPartitionTopologyImpl#artitionMap(boolean onlyActive) I get an assertion
because node2part.valid() is false. I spent a week in trying to understand what
does it mean and how it connected with the discovery ring, but failed.
> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
> Issue Type: Improvement
> Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Labels: important
> Fix For: 2.1
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F.
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A,
> etc.
> If some node leaves topology, adjacent nodes must reconnect.
> If nodes A, B, C are in same physical place, nodes D, E, F are in other
> place, and places lost connect each other, we will have many ways of
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where
> n -- number of nodes).
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet
> : other nodes). We will use it when we connect a new node.
> * [dev list
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding
> public static final constant to TcpDiscoverySpi.
> # Alter
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
> to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs
> are equal then we should compare nodes' IDs. This way we have consistent
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This
> can be postponed and implemented after we have other points done.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-4220) Allow to pass statements instead of strings to CacheStore.loadCache() implementations
[
https://issues.apache.org/jira/browse/IGNITE-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov resolved IGNITE-4220.
--
Resolution: Fixed
> Allow to pass statements instead of strings to CacheStore.loadCache()
> implementations
> -
>
> Key: IGNITE-4220
> URL: https://issues.apache.org/jira/browse/IGNITE-4220
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Alexei Kaigorodov
> Fix For: 2.1
>
>
> Currently both Cassandra store and POJO store allow user to provide a set of
> queries used for data loading. However, there are cases when user may want to
> provide a {{Statement}} instead (e.g., prepared statements with parameter
> binding are used). We should support {{Statement}} arguments in store
> implementations as well as strings.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5168) Expose IGFS metrics via an MBean or console Visor.
Ivan Veselovsky created IGNITE-5168: --- Summary: Expose IGFS metrics via an MBean or console Visor. Key: IGNITE-5168 URL: https://issues.apache.org/jira/browse/IGNITE-5168 Project: Ignite Issue Type: New Feature Components: IGFS Affects Versions: 2.0 Reporter: Ivan Veselovsky Assignee: Ivan Veselovsky Now in Ignite the only way to see IGFS metrics is to get them programmically from the code. But customers need them to understand what is cached in IGFS, so to expose the metrics would be useful. There are options to expose the metrics via MBean and/or via console Visor interface. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5167) ODBC: Abstract out handler and parser interfaces
[ https://issues.apache.org/jira/browse/IGNITE-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996556#comment-15996556 ] ASF GitHub Bot commented on IGNITE-5167: GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1907 IGNITE-5167 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5167 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1907.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1907 commit 0b06343240d0d8988629bc854ff6b2707bc9d85e Author: devozerov Date: 2017-05-04T11:07:59Z Done. commit e5f6141822edc00ae5225250701a0a90f85795ca Author: devozerov Date: 2017-05-04T11:08:39Z Minors. > ODBC: Abstract out handler and parser interfaces > > > Key: IGNITE-5167 > URL: https://issues.apache.org/jira/browse/IGNITE-5167 > Project: Ignite > Issue Type: Task > Components: jdbc-driver, odbc, SQL >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 2.1 > > > This is necessary for smooth thin JDBC driver integrration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5167) ODBC: Abstract out handler and parser interfaces
Vladimir Ozerov created IGNITE-5167: --- Summary: ODBC: Abstract out handler and parser interfaces Key: IGNITE-5167 URL: https://issues.apache.org/jira/browse/IGNITE-5167 Project: Ignite Issue Type: Task Components: jdbc-driver, odbc, SQL Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 2.1 This is necessary for smooth thin JDBC driver integrration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-2492) .NET: Peer assembly loading
[
https://issues.apache.org/jira/browse/IGNITE-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996551#comment-15996551
]
Pavel Tupitsyn commented on IGNITE-2492:
[~vozerov] I agree. Peer assembly loading should not be implemented within
binary marshaller, but only enabled for particular cases. We can have a common
wrapper object, {{PeerLoadingObjectHolder}}, which holds assembly information
along with the object itself, and perform peer requests during deserialization
if needed. This wrapper will be used only when peer loading is enabled and in
places where it is applicable.
> .NET: Peer assembly loading
> ---
>
> Key: IGNITE-2492
> URL: https://issues.apache.org/jira/browse/IGNITE-2492
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net
> Fix For: 2.1
>
>
> Similar to peer class loading in Java, we can provide a possibility to load
> assemblies on already started nodes, so that a node can execute jobs that are
> not present on other nodes.
> Considerations:
> * Can we unload assemblies after use to free memory? This requires a separate
> AppDomain, can we work with that?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4945) Web Console: Redesign filter controls for tables.
[ https://issues.apache.org/jira/browse/IGNITE-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-4945: Assignee: Andrey Novikov (was: Dmitriy Shabalin) Apply common input style to filters in table, pls review it > Web Console: Redesign filter controls for tables. > - > > Key: IGNITE-4945 > URL: https://issues.apache.org/jira/browse/IGNITE-4945 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Affects Versions: 1.9 >Reporter: Andrey Novikov >Assignee: Andrey Novikov > Attachments: Filtration.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4945) Web Console: Redesign filter controls for tables.
[ https://issues.apache.org/jira/browse/IGNITE-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-4945: Assignee: Dmitriy Shabalin (was: Vica Abramova) > Web Console: Redesign filter controls for tables. > - > > Key: IGNITE-4945 > URL: https://issues.apache.org/jira/browse/IGNITE-4945 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Affects Versions: 1.9 >Reporter: Andrey Novikov >Assignee: Dmitriy Shabalin > Attachments: Filtration.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5166) .NET: ComputeTaskSession
Pavel Tupitsyn created IGNITE-5166:
--
Summary: .NET: ComputeTaskSession
Key: IGNITE-5166
URL: https://issues.apache.org/jira/browse/IGNITE-5166
Project: Ignite
Issue Type: New Feature
Components: platforms
Reporter: Pavel Tupitsyn
See {{ComputeTaskSession}} in Java.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5071) Web Console: Support custom table names on model import
[ https://issues.apache.org/jira/browse/IGNITE-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996545#comment-15996545 ] Vasiliy Sisko commented on IGNITE-5071: --- Fixed alias generation. On import from database when a POJO generation is disabled an aliases generation is disabled too. > Web Console: Support custom table names on model import > --- > > Key: IGNITE-5071 > URL: https://issues.apache.org/jira/browse/IGNITE-5071 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 1.9 >Reporter: Alexey Kuznetsov >Assignee: Andrey Novikov > Fix For: 2.1 > > > We need to support table aliases aka custom table name on models import from > RDBMS. > See QueryEntity.TableName property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5165) Web Console: Buttons redesign
Dmitriy Shabalin created IGNITE-5165: Summary: Web Console: Buttons redesign Key: IGNITE-5165 URL: https://issues.apache.org/jira/browse/IGNITE-5165 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Dmitriy Shabalin Assignee: Ilya Borisov Create common style to all buttons in project. Refactoring current style for buttons in web-console/frontend/public/stylesheets/style.scss 1) Button with icon and text 2) Button with only icon 3) Button with only text 4) Button group 5) fill and stroke buttons for color Red, Blue, White Implement class modificator .btn-ignite to apply this features -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4991) Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is set
[
https://issues.apache.org/jira/browse/IGNITE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996532#comment-15996532
]
ASF GitHub Bot commented on IGNITE-4991:
GitHub user rfqu opened a pull request:
https://github.com/apache/ignite/pull/1906
Ignite 4991
issue IGNITE-4991 fixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rfqu/ignite ignite-4991
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1906.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1906
commit d6e7050280817b4705302346e170a1809a3d1a91
Author: Ivan Rakov
Date: 2017-05-03T08:24:01Z
IGNITE-5134: Fixed ClassCastException in IgniteCacheDatabaseSharedManager.
This closes #1895.
commit ff08c8e09033a1a703aae602c36a21565fbae606
Author: Anton Vinogradov
Date: 2017-05-03T09:49:18Z
Hibernate module deploy fix
commit af3bec468ebd82ccaba850843925b5709efe78d7
Author: rfqu
Date: 2017-05-04T10:08:27Z
issue fixed: IGNITE-4991
> Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is
> set
> -
>
> Key: IGNITE-4991
> URL: https://issues.apache.org/jira/browse/IGNITE-4991
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Alexei Kaigorodov
> Labels: newbie
> Fix For: 2.1
>
>
> {{IgniteKernal#ackSystemProperties}} and {{IgniteKernal#ackVmArguments}}
> print out system properties that can contain sensitive data. This print outs
> should be disabled when {{IGNITE_TO_STRING_INCLUDE_SENSITIVE}} system
> property is set to {{true}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-5164) Rename common ODBC/JDBC classes
[ https://issues.apache.org/jira/browse/IGNITE-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-5164. - Resolution: Fixed > Rename common ODBC/JDBC classes > --- > > Key: IGNITE-5164 > URL: https://issues.apache.org/jira/browse/IGNITE-5164 > Project: Ignite > Issue Type: Task > Components: jdbc-driver, odbc >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5164) Rename common ODBC/JDBC classes
Vladimir Ozerov created IGNITE-5164: --- Summary: Rename common ODBC/JDBC classes Key: IGNITE-5164 URL: https://issues.apache.org/jira/browse/IGNITE-5164 Project: Ignite Issue Type: Task Components: jdbc-driver, odbc Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 2.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-5143) Web console: Import of model required connection of agent to node
[ https://issues.apache.org/jira/browse/IGNITE-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov closed IGNITE-5143. -- Assignee: Alexey Kuznetsov (was: Andrey Novikov) > Web console: Import of model required connection of agent to node > - > > Key: IGNITE-5143 > URL: https://issues.apache.org/jira/browse/IGNITE-5143 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov > Fix For: 2.1 > > > Run agent without nodes. > Open Model page. > Try to import model from database. > Showed message that agent is not connected to node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5163) JDBC Driver: thin jdbc driver is based on pure TCP protocol
Taras Ledkov created IGNITE-5163: Summary: JDBC Driver: thin jdbc driver is based on pure TCP protocol Key: IGNITE-5163 URL: https://issues.apache.org/jira/browse/IGNITE-5163 Project: Ignite Issue Type: Task Components: jdbc-driver Affects Versions: 1.9 Reporter: Taras Ledkov Assignee: Taras Ledkov Fix For: 2.1 The GridClient must be removed from thin jdbc driver. It is the first step to unify JDBC & ODBC protocols. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5162) Get rid of version-depended ODBC server code
Vladimir Ozerov created IGNITE-5162: --- Summary: Get rid of version-depended ODBC server code Key: IGNITE-5162 URL: https://issues.apache.org/jira/browse/IGNITE-5162 Project: Ignite Issue Type: Task Components: odbc Affects Versions: 2.0 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 2.1 It is no longer needed as compatibility is broken. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5143) Web console: Import of model required connection of agent to node
[ https://issues.apache.org/jira/browse/IGNITE-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996469#comment-15996469 ] Vasiliy Sisko commented on IGNITE-5143: --- Tested. Anent not require a connection to a node on import of models. > Web console: Import of model required connection of agent to node > - > > Key: IGNITE-5143 > URL: https://issues.apache.org/jira/browse/IGNITE-5143 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Assignee: Andrey Novikov > Fix For: 2.1 > > > Run agent without nodes. > Open Model page. > Try to import model from database. > Showed message that agent is not connected to node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5118) Table with name Object lead to compilation error in code generated by webconsole
[ https://issues.apache.org/jira/browse/IGNITE-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-5118: - Assignee: Andrey Novikov (was: Vasiliy Sisko) > Table with name Object lead to compilation error in code generated by > webconsole > > > Key: IGNITE-5118 > URL: https://issues.apache.org/jira/browse/IGNITE-5118 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.7 >Reporter: Evgenii Zhuravlev >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5118) Table with name Object lead to compilation error in code generated by webconsole
[ https://issues.apache.org/jira/browse/IGNITE-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996450#comment-15996450 ] Vasiliy Sisko commented on IGNITE-5118: --- Fixed type name generation when type name is a Java class name. > Table with name Object lead to compilation error in code generated by > webconsole > > > Key: IGNITE-5118 > URL: https://issues.apache.org/jira/browse/IGNITE-5118 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.7 >Reporter: Evgenii Zhuravlev >Assignee: Vasiliy Sisko > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4922) JDBC Driver: renew thin client based solution
[
https://issues.apache.org/jira/browse/IGNITE-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996449#comment-15996449
]
Vladimir Ozerov commented on IGNITE-4922:
-
Proposed implementation plan:
1) Merge ODBC and thin driver on server side. ODBC should use
{{BinaryMarshaller}}, JDBC should use {{JdkMarshaller}};
2) Introduce {{SqlListenerConfiguration}}, which will be a copy of
{{OdbcConfiguration}}, deprecate the latter;
3) Implement new driver from scratch, using {{GridNioServer}} as a base.
> JDBC Driver: renew thin client based solution
> -
>
> Key: IGNITE-4922
> URL: https://issues.apache.org/jira/browse/IGNITE-4922
> Project: Ignite
> Issue Type: Task
>Reporter: Denis Magda
> Fix For: 2.1
>
>
> This is a parent ticket for all the activities that are intended to improve
> the thin client based implementation of the JDBC driver making it default one.
>
> Refer to the corresponding discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/jdbc-vs-jdbc2-packages-td14309.html
> In a nutshell, depending on a type of a protocol to be used for the next-gen
> version the options are the following:
> - This type of driver might be a default driver for tools and applications
> that don't need transactional support. Existing REST based protocol can be
> used for this scenario.
> - If we want to support transactions (which is optional at the beginning)
> then Yakov solution (see discussion) can be applied. However, it makes sense
> to implement it only after MVCC is ready.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4976) Document C++ Continuous Queries Remote Filters
[ https://issues.apache.org/jira/browse/IGNITE-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-4976: --- Assignee: Denis Magda (was: Igor Sapego) > Document C++ Continuous Queries Remote Filters > -- > > Key: IGNITE-4976 > URL: https://issues.apache.org/jira/browse/IGNITE-4976 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 1.9 >Reporter: Denis Magda >Assignee: Denis Magda > Labels: cpp, documentation > Fix For: 2.1 > > > [~isapego], please document CQ remote filters feature (IGNITE-3575) and > assign the ticket on me and Prachi for the final modifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4976) Document C++ Continuous Queries Remote Filters
[ https://issues.apache.org/jira/browse/IGNITE-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996434#comment-15996434 ] Igor Sapego commented on IGNITE-4976: - [~dmagda], done. Here is the link for review: https://apacheignite-cpp.readme.io/v2.0/docs/continuous-queries-21 > Document C++ Continuous Queries Remote Filters > -- > > Key: IGNITE-4976 > URL: https://issues.apache.org/jira/browse/IGNITE-4976 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 1.9 >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, documentation > Fix For: 2.1 > > > [~isapego], please document CQ remote filters feature (IGNITE-3575) and > assign the ticket on me and Prachi for the final modifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5118) Table with name Object lead to compilation error in code generated by webconsole
[ https://issues.apache.org/jira/browse/IGNITE-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-5118: - Assignee: Vasiliy Sisko (was: Alexey Kuznetsov) > Table with name Object lead to compilation error in code generated by > webconsole > > > Key: IGNITE-5118 > URL: https://issues.apache.org/jira/browse/IGNITE-5118 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.7 >Reporter: Evgenii Zhuravlev >Assignee: Vasiliy Sisko > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4976) Document C++ Continuous Queries Remote Filters
[ https://issues.apache.org/jira/browse/IGNITE-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996421#comment-15996421 ] Igor Sapego commented on IGNITE-4976: - Also, sorry, I forgot to mention before, but I've already filed ticket for example improvement - IGNITE-5154 > Document C++ Continuous Queries Remote Filters > -- > > Key: IGNITE-4976 > URL: https://issues.apache.org/jira/browse/IGNITE-4976 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 1.9 >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, documentation > Fix For: 2.1 > > > [~isapego], please document CQ remote filters feature (IGNITE-3575) and > assign the ticket on me and Prachi for the final modifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4976) Document C++ Continuous Queries Remote Filters
[ https://issues.apache.org/jira/browse/IGNITE-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996415#comment-15996415 ] Igor Sapego commented on IGNITE-4976: - [~dmagda], actually, this code is present in code snippet below. But I guess it has become too big so it's hard to notice now. I will split it in several parts and put code in several tabs, so it's easier to read. Let's see if it helps. > Document C++ Continuous Queries Remote Filters > -- > > Key: IGNITE-4976 > URL: https://issues.apache.org/jira/browse/IGNITE-4976 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 1.9 >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, documentation > Fix For: 2.1 > > > [~isapego], please document CQ remote filters feature (IGNITE-3575) and > assign the ticket on me and Prachi for the final modifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-5160) C++ Continuous Queries example has to demonstrate the filter usage
[ https://issues.apache.org/jira/browse/IGNITE-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-5160. - Resolution: Duplicate Closed as a duplicate of IGNITE-5154 > C++ Continuous Queries example has to demonstrate the filter usage > -- > > Key: IGNITE-5160 > URL: https://issues.apache.org/jira/browse/IGNITE-5160 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Assignee: Igor Sapego > Fix For: 2.1 > > > The existing continuous queries example [1] has to be extended to the usage > of a remote filter explained here [2]. > [1] > https://github.com/apache/ignite/blob/master/modules/platforms/cpp/examples/continuous-query-example/src/continuous_query_example.cpp > [2] > https://apacheignite-cpp.readme.io/docs/continuous-queries#section-remote-filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5128) Support queries for GridClientData
[
https://issues.apache.org/jira/browse/IGNITE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996385#comment-15996385
]
ASF GitHub Bot commented on IGNITE-5128:
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/1905
IGNITE-5128 Support queries for GridClientData
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5128
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1905.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1905
commit 67d0f08a0ff26d59cc6ef8ed57efd0b682779f78
Author: tledkov-gridgain
Date: 2017-05-03T10:52:17Z
IGNITE-5128: Support queries for GridClientData based on rest protocol
commit 2d1dd52f291e8471cd6f194ef76a3130c72d57cb
Author: tledkov-gridgain
Date: 2017-05-04T08:54:14Z
Merge branch '_master' into ignite-5128
> Support queries for GridClientData
> --
>
> Key: IGNITE-5128
> URL: https://issues.apache.org/jira/browse/IGNITE-5128
> Project: Ignite
> Issue Type: Task
> Components: clients, jdbc-driver
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> Now a query is executed via client compute API. Creates the task, task
> creates a job, job executes SQL query then results are reduced by task and
> sent to a client as a task results.
> Implementation plan:
> * Add the method {{ClientCursor GridClientData.query(String, Object.. args)}};
> * Add the client messages to execute query and results paging to the
> {{org.apache.ignite.internal.processors.rest.client.message}};
> * Implement query protocol at the {{GridClientNioTcpConnection}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-5086) Web Console: Redesign of Modal Windows
[ https://issues.apache.org/jira/browse/IGNITE-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996370#comment-15996370 ] Dmitriy Shabalin edited comment on IGNITE-5086 at 5/4/17 8:48 AM: -- Resign modals. Implemented new view on admin page to activities detail. Pls, review it was (Author: dmitriyff): Resign modals. Pls, review it > Web Console: Redesign of Modal Windows > -- > > Key: IGNITE-5086 > URL: https://issues.apache.org/jira/browse/IGNITE-5086 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Affects Versions: 2.1 >Reporter: Vica Abramova >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5086) Web Console: Redesign of Modal Windows
[ https://issues.apache.org/jira/browse/IGNITE-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-5086: Assignee: Andrey Novikov (was: Dmitriy Shabalin) Pls, review it > Web Console: Redesign of Modal Windows > -- > > Key: IGNITE-5086 > URL: https://issues.apache.org/jira/browse/IGNITE-5086 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Affects Versions: 2.1 >Reporter: Vica Abramova >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-5086) Web Console: Redesign of Modal Windows
[ https://issues.apache.org/jira/browse/IGNITE-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996370#comment-15996370 ] Dmitriy Shabalin edited comment on IGNITE-5086 at 5/4/17 8:47 AM: -- Resign modals. Pls, review it was (Author: dmitriyff): Pls, review it > Web Console: Redesign of Modal Windows > -- > > Key: IGNITE-5086 > URL: https://issues.apache.org/jira/browse/IGNITE-5086 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Affects Versions: 2.1 >Reporter: Vica Abramova >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization
[ https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996349#comment-15996349 ] ASF GitHub Bot commented on IGNITE-1094: GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/1904 IGNITE-1094 corrupted cache recovery resolved You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite Ignite-1094 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1904.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1904 commit e47ce114e6431cc55e58ea2fdcbdc53b93ea57df Author: voipp Date: 2017-05-03T13:22:19Z IGNITE-1094 corrupted cache recovery resolved > Ignite.createCache(CacheConfiguration) hangs if some exception occurs during > cache initialization > - > > Key: IGNITE-1094 > URL: https://issues.apache.org/jira/browse/IGNITE-1094 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Sergey Evdokimov >Assignee: Alexey Kuznetsov > Labels: Muted_test > Fix For: 2.1 > > > User can pass broken configuration, for example, store factory that throws > exception from create() method. I created test to demonstrate the problem. > See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' > branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-2492) .NET: Peer assembly loading
[ https://issues.apache.org/jira/browse/IGNITE-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996342#comment-15996342 ] Vladimir Ozerov commented on IGNITE-2492: - [~ptupitsyn], I'd like to mention that data and code should not be mixed as a part of this feature implementation. That is, data layer is already well abstracted with help of binary marshalling. Peer-assembly-loading should be used only for code (compute, services, listeners, etc.). We can start with compute component first. > .NET: Peer assembly loading > --- > > Key: IGNITE-2492 > URL: https://issues.apache.org/jira/browse/IGNITE-2492 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net > Fix For: 2.1 > > > Similar to peer class loading in Java, we can provide a possibility to load > assemblies on already started nodes, so that a node can execute jobs that are > not present on other nodes. > Considerations: > * Can we unload assemblies after use to free memory? This requires a separate > AppDomain, can we work with that? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5082) Redesign base template
[ https://issues.apache.org/jira/browse/IGNITE-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-5082: Assignee: Andrey Novikov (was: Ilya Borisov) Please review. > Redesign base template > -- > > Key: IGNITE-5082 > URL: https://issues.apache.org/jira/browse/IGNITE-5082 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Affects Versions: 2.1 >Reporter: Dmitriy Shabalin >Assignee: Andrey Novikov > Fix For: 2.1 > > Attachments: base layout.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-4437) Make sure data structures do not use outTx call
[ https://issues.apache.org/jira/browse/IGNITE-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-4437. -- Resolution: Fixed Fix Version/s: (was: 2.1) 2.0 Done as part of IGNITE-2893 (#ee955df9fb80737292aac5f7ad3c82f8f0d8ea8e). Closing this issue. > Make sure data structures do not use outTx call > --- > > Key: IGNITE-4437 > URL: https://issues.apache.org/jira/browse/IGNITE-4437 > Project: Ignite > Issue Type: Improvement > Components: cache, data structures >Reporter: Alexei Scherbakov >Assignee: Ryabov Dmitrii > Labels: newbie > Fix For: 2.0 > > > Ignite's data structures use outTx call to avoid an intersection with user > transaction. > This is no longer necessary, because system and user transactions are now > separated. > Need to get rid of these calls. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
