[jira] [Updated] (IGNITE-5368) Cassandra store should support private/public fields serialization for POJO persistence strategy
[ https://issues.apache.org/jira/browse/IGNITE-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Rudyak updated IGNITE-5368: Description: As for now for POJO persistence strategy, Cassandra cache store supports only java classes following JavaBeans convention (having getters & setters). It should also support serialization/deserialization for public/private class fields which are not following JavaBeans convention but: - Annotated with @QuerySqlField and @AffinityKeyMapped - Manually specified in persistence descriptor was: As for now for POJO persistence strategy, Cassandra cache store supports only java classes following JavaBeans convention (having getters & setters). It should also support serialization/deserialization for public/private class fields which are not following JavaBeans convention but: - Annotated with @QuerySqlField - Manually specified in persistence descriptor > Cassandra store should support private/public fields serialization for POJO > persistence strategy > > > Key: IGNITE-5368 > URL: https://issues.apache.org/jira/browse/IGNITE-5368 > Project: Ignite > Issue Type: Improvement > Components: cassandra >Reporter: Igor Rudyak >Assignee: Igor Rudyak > > As for now for POJO persistence strategy, Cassandra cache store supports only > java classes following JavaBeans convention (having getters & setters). > It should also support serialization/deserialization for public/private class > fields which are not following JavaBeans convention but: > - Annotated with @QuerySqlField and @AffinityKeyMapped > - Manually specified in persistence descriptor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5208) CPP: Segfault on Put
[
https://issues.apache.org/jira/browse/IGNITE-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5208:
Summary: CPP: Segfault on Put (was: C++ Segfault on Put)
> CPP: Segfault on Put
>
>
> Key: IGNITE-5208
> URL: https://issues.apache.org/jira/browse/IGNITE-5208
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Tolga HOŞGÖR
>Assignee: Igor Sapego
>Priority: Critical
> Labels: c++, cpp
> Fix For: 2.1
>
>
> The following segfault happens when:
> - using multiple caches (suffixed with number as in X_\{number\}),
> - caches contain same type of object but not the same objects,
> - doing multithreaded `::Put` operation, only one put is done on each cache
> concurrently, independent caches (X_1, X_2, ...) can be operated on and
> called `::Put` on concurrently, but that should not be relevant as cache api
> is thread safe.
> {code:none}
> C [test+0xf8116a] std::less::operator()(int const&, int const&)
> const+0x14
> C [test+0x1106305] std::_Rb_tree ignite::common::concurrent::SharedPointer
> >, std::_Select1st ignite::common::concurrent::SharedPointer
> > >, std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::_M_lower_bound(std::_Rb_tree_node ignite::common::concurrent::SharedPointer
> > >*, std::_Rb_tree_node_base*, int const&)+0x41
> C [test+0x1105a9d] std::_Rb_tree ignite::common::concurrent::SharedPointer
> >, std::_Select1st ignite::common::concurrent::SharedPointer
> > >, std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::find(int const&)+0x45
> C [test+0x1104e7f] std::map ignite::common::concurrent::SharedPointer,
> std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::find(int const&)+0x23
> C [test+0x1104031]
> ignite::impl::binary::BinaryTypeManager::GetHandler(std::__cxx11::basic_string std::char_traits, std::allocator > const&, int)+0x6f
> C [test+0xe6de2d] void
> ignite::impl::binary::BinaryWriterImpl::WriteTopObject
> >(std::shared_ptr const&)+0xbb
> C [test+0xe6cd48]
> ignite::impl::In2Operation std::char_traits, std::allocator >, std::shared_ptr
> >::ProcessInput(ignite::impl::binary::BinaryWriterImpl&)+0x3e
> C [test+0x1128cf1]
> ignite::impl::interop::InteropTarget::WriteTo(ignite::impl::interop::InteropMemory*,
> ignite::impl::InputOperation&, ignite::IgniteError&)+0xa9
> C [test+0x1128f67] ignite::impl::interop::InteropTarget::OutOp(int,
> ignite::impl::InputOperation&, ignite::IgniteError&)+0x65
> C [test+0x1125f41]
> ignite::impl::cache::CacheImpl::Put(ignite::impl::InputOperation&,
> ignite::IgniteError&)+0x2d
> C [test+0xe5539a] ignite::cache::Cache std::char_traits, std::allocator >, std::shared_ptr
> >::Put(std::__cxx11::basic_string,
> std::allocator > const&, std::shared_ptr const&,
> ignite::IgniteError&)+0x52
> {code}
> There seems to be some kind of race situation:
> {code:none}
> 0x01381206 in std::less::operator() (this=0x1a4e4b0, __x= reading variable>, __y=@0x7fff80846e04: 2066246303) at
> /usr/include/c++/6.3.1/bits/stl_function.h:386
> {code}
> {code:none}
> #4 0x015040cd in ignite::impl::binary::BinaryTypeManager::GetHandler
> (this=0x1a560d0, typeName="test.data", typeId=2066246303) at
> src/impl/binary/binary_type_manager.cpp:56
> 56 std::map::iterator it =
> snapshots0.find(typeId);
> (gdb) print snapshots0
> $10 = std::map with 42286576 elements = {[42312864] = {ptr = 0x285a4a0, impl
> = 0x0}...}
> (gdb) print snapshot
> $11 = {ptr = 0x7fffda4f, impl = 0x11}
> {code}
> `impl` pointers seems to be corrupted on multiple places.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5273) .NET: MemoryMetrics API improvements to be ported to .NET
[ https://issues.apache.org/jira/browse/IGNITE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5273: Labels: .NET important (was: important) > .NET: MemoryMetrics API improvements to be ported to .NET > - > > Key: IGNITE-5273 > URL: https://issues.apache.org/jira/browse/IGNITE-5273 > Project: Ignite > Issue Type: Task > Components: general, platforms >Reporter: Sergey Chugunov >Assignee: Pavel Tupitsyn > Labels: .NET, important > Fix For: 2.1 > > > Improvements already made for linked ticket need to be ported on .NET side. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5337) CPP: linux examples: names of executable files should be the same type
[ https://issues.apache.org/jira/browse/IGNITE-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5337: Summary: CPP: linux examples: names of executable files should be the same type (was: C++ linux examples: names of executable files should be the same type) > CPP: linux examples: names of executable files should be the same type > -- > > Key: IGNITE-5337 > URL: https://issues.apache.org/jira/browse/IGNITE-5337 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 2.0 >Reporter: Irina Zaporozhtseva >Assignee: Igor Sapego >Priority: Minor > Labels: cpp, examples > Fix For: 2.1 > > > C++ linux examples: make executable file names the same type: > ignate--example > now names are: > ignite-continuous-query-example > ignite-odbcexample > ignite-putgetexample > ignite-queryexample -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5208) C++ Segfault on Put
[
https://issues.apache.org/jira/browse/IGNITE-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5208:
Labels: c++ cpp (was: c++)
> C++ Segfault on Put
> ---
>
> Key: IGNITE-5208
> URL: https://issues.apache.org/jira/browse/IGNITE-5208
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Tolga HOŞGÖR
>Assignee: Igor Sapego
>Priority: Critical
> Labels: c++, cpp
> Fix For: 2.1
>
>
> The following segfault happens when:
> - using multiple caches (suffixed with number as in X_\{number\}),
> - caches contain same type of object but not the same objects,
> - doing multithreaded `::Put` operation, only one put is done on each cache
> concurrently, independent caches (X_1, X_2, ...) can be operated on and
> called `::Put` on concurrently, but that should not be relevant as cache api
> is thread safe.
> {code:none}
> C [test+0xf8116a] std::less::operator()(int const&, int const&)
> const+0x14
> C [test+0x1106305] std::_Rb_tree ignite::common::concurrent::SharedPointer
> >, std::_Select1st ignite::common::concurrent::SharedPointer
> > >, std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::_M_lower_bound(std::_Rb_tree_node ignite::common::concurrent::SharedPointer
> > >*, std::_Rb_tree_node_base*, int const&)+0x41
> C [test+0x1105a9d] std::_Rb_tree ignite::common::concurrent::SharedPointer
> >, std::_Select1st ignite::common::concurrent::SharedPointer
> > >, std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::find(int const&)+0x45
> C [test+0x1104e7f] std::map ignite::common::concurrent::SharedPointer,
> std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::find(int const&)+0x23
> C [test+0x1104031]
> ignite::impl::binary::BinaryTypeManager::GetHandler(std::__cxx11::basic_string std::char_traits, std::allocator > const&, int)+0x6f
> C [test+0xe6de2d] void
> ignite::impl::binary::BinaryWriterImpl::WriteTopObject
> >(std::shared_ptr const&)+0xbb
> C [test+0xe6cd48]
> ignite::impl::In2Operation std::char_traits, std::allocator >, std::shared_ptr
> >::ProcessInput(ignite::impl::binary::BinaryWriterImpl&)+0x3e
> C [test+0x1128cf1]
> ignite::impl::interop::InteropTarget::WriteTo(ignite::impl::interop::InteropMemory*,
> ignite::impl::InputOperation&, ignite::IgniteError&)+0xa9
> C [test+0x1128f67] ignite::impl::interop::InteropTarget::OutOp(int,
> ignite::impl::InputOperation&, ignite::IgniteError&)+0x65
> C [test+0x1125f41]
> ignite::impl::cache::CacheImpl::Put(ignite::impl::InputOperation&,
> ignite::IgniteError&)+0x2d
> C [test+0xe5539a] ignite::cache::Cache std::char_traits, std::allocator >, std::shared_ptr
> >::Put(std::__cxx11::basic_string,
> std::allocator > const&, std::shared_ptr const&,
> ignite::IgniteError&)+0x52
> {code}
> There seems to be some kind of race situation:
> {code:none}
> 0x01381206 in std::less::operator() (this=0x1a4e4b0, __x= reading variable>, __y=@0x7fff80846e04: 2066246303) at
> /usr/include/c++/6.3.1/bits/stl_function.h:386
> {code}
> {code:none}
> #4 0x015040cd in ignite::impl::binary::BinaryTypeManager::GetHandler
> (this=0x1a560d0, typeName="test.data", typeId=2066246303) at
> src/impl/binary/binary_type_manager.cpp:56
> 56 std::map::iterator it =
> snapshots0.find(typeId);
> (gdb) print snapshots0
> $10 = std::map with 42286576 elements = {[42312864] = {ptr = 0x285a4a0, impl
> = 0x0}...}
> (gdb) print snapshot
> $11 = {ptr = 0x7fffda4f, impl = 0x11}
> {code}
> `impl` pointers seems to be corrupted on multiple places.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
[ https://issues.apache.org/jira/browse/IGNITE-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5315: Labels: .NET (was: ) > .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll) > --- > > Key: IGNITE-5315 > URL: https://issues.apache.org/jira/browse/IGNITE-5315 > Project: Ignite > Issue Type: Task > Components: platforms, sql >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > > Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. > Need to investigate why and fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (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 ] Aleksey Chetaev updated IGNITE-5160: Labels: cpp important (was: important) > 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 > Components: platforms >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, important > 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] [Updated] (IGNITE-5160) CPP: 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 ] Aleksey Chetaev updated IGNITE-5160: Summary: CPP: Continuous Queries example has to demonstrate the filter usage (was: C++ Continuous Queries example has to demonstrate the filter usage) > CPP: 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 > Components: platforms >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, important > 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] [Updated] (IGNITE-5154) CPP: Add remote filter to continuous queries C++ example.
[ https://issues.apache.org/jira/browse/IGNITE-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5154: Labels: cpp important (was: important) > CPP: Add remote filter to continuous queries C++ example. > - > > Key: IGNITE-5154 > URL: https://issues.apache.org/jira/browse/IGNITE-5154 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.9 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: cpp, important > Fix For: 2.1 > > > As we have added support for the remote filters for Ignite C++ (IGNITE-3575), > we now need to modify continuous queries C++ example by adding remote filter > to it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5135) .NET: Improve remote error propagation
[
https://issues.apache.org/jira/browse/IGNITE-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5135:
Labels: .NET (was: )
> .NET: Improve remote error propagation
> --
>
> Key: IGNITE-5135
> URL: https://issues.apache.org/jira/browse/IGNITE-5135
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.1
>
>
> When we rethrow remote exceptions, we should wrap them in another exception
> to preserve remote stack traces.
> For example, {{ComputeAbstractClosureTask.OnResult}} uses {{throw err}},
> where {{err}} is a deserialized remote exception. This call causes remote
> stack trace loss.
> Instead we should do {{throw new IgniteException("Remote computation failed",
> err)}} which will preserve remote stack trace.
> Same should be done for other remote invocation scenarios (event listeners
> and so on).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5001) .NET: Tests cleanup
[
https://issues.apache.org/jira/browse/IGNITE-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5001:
Labels: .net (was: )
> .NET: Tests cleanup
> ---
>
> Key: IGNITE-5001
> URL: https://issues.apache.org/jira/browse/IGNITE-5001
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
> Labels: .net
> Fix For: 2.1
>
>
> * Use {{GetTestConfiguration}} where possible
> * Make sure {{Localhost}} is set in all other cases to avoid external node
> discovery
> * Remove binary type configuration where it is not necessary
> * Get rid of Spring XML where it is not needed (Events, Messaging, etc)
> * Replace try-catch with {{Assert.Throws}} where possible
> * Make sure {{Ignition.StopAll}} is present where needed
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035255#comment-16035255 ] ASF GitHub Bot commented on IGNITE-5355: GitHub user achetaev opened a pull request: https://github.com/apache/ignite/pull/2073 IGNITE-5355 Create task with release tools You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5355 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2073.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 #2073 commit a6ad620cece5be02da4f8394a501f7c7fd76f165 Author: Aleksey Chetaev Date: 2017-06-01T15:00:21Z IGNITE-5355: Added new class to ignite-tools for generate release report commit 1aeee2062d48324712bc51c1b6cde9969d58cacc Author: Aleksey Chetaev Date: 2017-06-01T15:17:10Z Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite into ignite-5355 commit 42876c924e7ccbd84b3883acae21d069aa971b34 Author: Aleksey Chetaev Date: 2017-06-01T17:23:43Z IGNITE-5355 Add needed dependencies to tools/pom.xml commit dcb5cca3b923ad2c5fffcf85b24fe062b109d74c Author: Aleksey Chetaev Date: 2017-06-02T13:13:20Z IGNITE-5355 Implemet reports templates for customise reports withou code change > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev > > 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4636) .NET: Support local collection joins in LINQ
[
https://issues.apache.org/jira/browse/IGNITE-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035004#comment-16035004
]
Sergey Stronchinskiy commented on IGNITE-4636:
--
[~ptupitsyn],
Yes, it is one of the problems in implementation of join with local collections
in compiled queries with collection passed as a parameter.
> .NET: Support local collection joins in LINQ
>
>
> Key: IGNITE-4636
> URL: https://issues.apache.org/jira/browse/IGNITE-4636
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
> Labels: .NET, LINQ
> Fix For: 2.1
>
>
> LINQ {{IN}} clause is implemented in IGNITE-4425 and maps from
> {{ICollection.Contains}}.
> However, {{IN}} has some limitations in Ignite, and better alternative is
> temporary table join:
> https://apacheignite.readme.io/docs/sql-performance-and-debugging#sql-performance-and-usability-considerations
> Example SQL:
> {code}
> new SqlFieldsQuery("select p.name from Person p join table(id bigint = ?) i
> on p.OrgId = i.id", new object[] { new object[] {1,3}})
> {code}
> Add support in LINQ like this:
> {code}persons.AsCacheQueryable().Join(new[] {1, 3}, p => p.Value.OrgId, x =>
> x, (p, x) => p);{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4636) .NET: Support local collection joins in LINQ
[
https://issues.apache.org/jira/browse/IGNITE-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034969#comment-16034969
]
Pavel Tupitsyn commented on IGNITE-4636:
[~GuruStron] looks like a bug on Java side to me. I'll investigate and file it.
Does it affect this task?
> .NET: Support local collection joins in LINQ
>
>
> Key: IGNITE-4636
> URL: https://issues.apache.org/jira/browse/IGNITE-4636
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
> Labels: .NET, LINQ
> Fix For: 2.1
>
>
> LINQ {{IN}} clause is implemented in IGNITE-4425 and maps from
> {{ICollection.Contains}}.
> However, {{IN}} has some limitations in Ignite, and better alternative is
> temporary table join:
> https://apacheignite.readme.io/docs/sql-performance-and-debugging#sql-performance-and-usability-considerations
> Example SQL:
> {code}
> new SqlFieldsQuery("select p.name from Person p join table(id bigint = ?) i
> on p.OrgId = i.id", new object[] { new object[] {1,3}})
> {code}
> Add support in LINQ like this:
> {code}persons.AsCacheQueryable().Join(new[] {1, 3}, p => p.Value.OrgId, x =>
> x, (p, x) => p);{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4636) .NET: Support local collection joins in LINQ
[
https://issues.apache.org/jira/browse/IGNITE-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034967#comment-16034967
]
Sergey Stronchinskiy commented on IGNITE-4636:
--
[~ptupitsyn],
While working on this feature found that {{SqlFieldsQuery}} fails if it is
passed collection of {{int}}'s instead of {{objects}}:
{code}
employeeCache.QueryFields(new SqlFieldsQuery("select p.name, p.salary from
Employee p join table(id bigint = ?) i on p.organizationid = i.id"
, new object[] { new [] { 1, 3 } }));
{code}
> .NET: Support local collection joins in LINQ
>
>
> Key: IGNITE-4636
> URL: https://issues.apache.org/jira/browse/IGNITE-4636
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
> Labels: .NET, LINQ
> Fix For: 2.1
>
>
> LINQ {{IN}} clause is implemented in IGNITE-4425 and maps from
> {{ICollection.Contains}}.
> However, {{IN}} has some limitations in Ignite, and better alternative is
> temporary table join:
> https://apacheignite.readme.io/docs/sql-performance-and-debugging#sql-performance-and-usability-considerations
> Example SQL:
> {code}
> new SqlFieldsQuery("select p.name from Person p join table(id bigint = ?) i
> on p.OrgId = i.id", new object[] { new object[] {1,3}})
> {code}
> Add support in LINQ like this:
> {code}persons.AsCacheQueryable().Join(new[] {1, 3}, p => p.Value.OrgId, x =>
> x, (p, x) => p);{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4370) ODBC: Implement DML operations with parameters in batch.
[
https://issues.apache.org/jira/browse/IGNITE-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034900#comment-16034900
]
Igor Sapego commented on IGNITE-4370:
-
Useful MS article with details of the API and implementation:
https://docs.microsoft.com/en-us/sql/odbc/reference/develop-app/using-arrays-of-parameters
> ODBC: Implement DML operations with parameters in batch.
>
>
> Key: IGNITE-4370
> URL: https://issues.apache.org/jira/browse/IGNITE-4370
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: important
> Fix For: 2.1
>
>
> Currently, if user wants for example to insert 20k records they need to call
> {{SQLExecute}} for the 20k times. More than that, internally, we transmit and
> execute the same SQL query 20k times. This is a huge overhead. We should only
> transfer sql query once, transfer all the parameters in a batch and then
> execute it once using some fast, possibly internal API.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-5152) .NET: BinaryMarshaller should write ints in "varint" encoding where it makes sense
[ https://issues.apache.org/jira/browse/IGNITE-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur reassigned IGNITE-5152: -- Assignee: Vyacheslav Daradur > .NET: BinaryMarshaller should write ints in "varint" encoding where it makes > sense > -- > > Key: IGNITE-5152 > URL: https://issues.apache.org/jira/browse/IGNITE-5152 > Project: Ignite > Issue Type: Sub-task > Components: general >Affects Versions: 2.0 >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur > Fix For: 2.1 > > > Need to implement IGNITE-5097 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5293) Replicated cache performance degradation.
[
https://issues.apache.org/jira/browse/IGNITE-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov reassigned IGNITE-5293:
-
Assignee: Semen Boikov
> Replicated cache performance degradation.
> -
>
> Key: IGNITE-5293
> URL: https://issues.apache.org/jira/browse/IGNITE-5293
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Alexei Scherbakov
>Assignee: Semen Boikov
> Fix For: 2.2
>
>
> With increase in number of nodes puts to replicated cache are slowed down
> almost in the same proportion.
> Unit test reproducer:
> {noformat}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one or more
> * contributor license agreements. See the NOTICE file distributed with
> * this work for additional information regarding copyright ownership.
> * The ASF licenses this file to You under the Apache License, Version 2.0
> * (the "License"); you may not use this file except in compliance with
> * the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.ignite.internal.processors.cache.distributed.replicated;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.MemoryConfiguration;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> /**
> * Tests replicated cache performance .
> */
> public class GridCacheReplicatedTransactionalDegradationTest extends
> GridCommonAbstractTest {
> /** Keys. */
> private static final int KEYS = 100_000;
> @Override protected IgniteConfiguration getConfiguration(String gridName)
> throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(gridName);
> cfg.setClientMode(gridName.startsWith("client"));
> CacheConfiguration ccfg = new CacheConfiguration();
> ccfg.setCacheMode(CacheMode.REPLICATED);
> ccfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
>
> ccfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
> ccfg.setName("test");
> cfg.setCacheConfiguration(ccfg);
> return cfg;
> }
> /** */
> public void testThroughput() throws Exception {
> try {
> IgniteEx grid0 = startGrid(0);
> Ignite client = startGrid("client");
> IgniteCache cache =
> client.getOrCreateCache("test");
> doTest(client, cache);
> startGrid(1);
> doTest(client, cache);
> startGrid(2);
> doTest(client, cache);
> } finally {
> stopAllGrids();
> }
> }
> /**
> * @param client
> * @param cache Cache.
> */
> private void doTest(Ignite client, IgniteCache cache) {
> long t1 = System.currentTimeMillis();
> for (int i = 0; i < KEYS; i++) {
> try (Transaction tx =
> client.transactions().txStart(TransactionConcurrency.PESSIMISTIC,
> TransactionIsolation.REPEATABLE_READ)) {
> cache.put(i, i);
> tx.commit();
> }
> }
> log.info("TPS: " + Math.round(KEYS /
> (float)(System.currentTimeMillis() - t1) * 1000));
> }
> }
> {noformat}
> My test results are:
> 1. transactional cache, explicit transaction.
> TPS: 2507
> TPS: 1660
> TPS: 1148
> 2. atomic cache
> TPS: 6416
> TPS: 5177
> TPS: 4403
> 3. transactional cache, no explicit transaction
> TPS: 4485
> TPS: 2289
> TPS: 1439
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5263) ODBC: use schema notion instead of cache name
[ https://issues.apache.org/jira/browse/IGNITE-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034846#comment-16034846 ] ASF GitHub Bot commented on IGNITE-5263: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2071 IGNITE-5263: Replaced ODBC connection param "Cache" with "Schema" You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5263 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2071.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 #2071 commit f37fada5e4ad5730f20ae964db30fd84d3e207c4 Author: Igor Sapego Date: 2017-06-01T17:00:16Z IGNITE-5263: Renamed cache connection param to Schema commit 6a23f1fbfd5c2013ad8713dc4d9646f98af955f2 Author: Igor Sapego Date: 2017-06-02T12:24:01Z IGNITE-5263: Implmented on Java side commit 59701054b55d2ab7f7bbf1abca4b95aabb2c53cb Author: Igor Sapego Date: 2017-06-02T14:34:25Z IGNITE-5263: Minor fixes > ODBC: use schema notion instead of cache name > - > > Key: IGNITE-5263 > URL: https://issues.apache.org/jira/browse/IGNITE-5263 > Project: Ignite > Issue Type: Task > Components: odbc, sql >Reporter: Vladimir Ozerov >Assignee: Igor Sapego > Labels: cpp, odbc > Fix For: 2.1 > > > We should no longer operate on "cacheName". Instead, we should work with > schemas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5293) Replicated cache performance degradation.
[
https://issues.apache.org/jira/browse/IGNITE-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034840#comment-16034840
]
Yakov Zhdanov commented on IGNITE-5293:
---
In this pull request I tried to remove minifutures and compound futures from
DhtLockFuture, DhtTxPrepareFuture and DhtTxFinishFuture -
https://github.com/apache/ignite/pull/2070. We need to test it on TC and run
benchmarks to see if it helps.
Here is the test that runs eternally and may be helpful for local reproducing.
{noformat}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.ignite;
import java.util.concurrent.ThreadLocalRandom;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.CacheWriteSynchronizationMode;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;
import org.jsr166.LongAdder8;
/**
*
*/
public class ReplBench {
public static void main(String[] args) {
for (int i = 0; i < Integer.parseInt(args[0]); i++) {
Ignition.start(config());
}
Ignition.setClientMode(true);
final Ignite ignite = Ignition.start(config());
final LongAdder8 cnt = new LongAdder8();
final IgniteCache replCache = ignite.getOrCreateCache(
new CacheConfiguration("REPL")
.setCacheMode(CacheMode.REPLICATED)
.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL)
.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC));
new Thread(
new Runnable() {
@Override
public void run() {
for (;;) {
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
e.printStackTrace();
}
System.out.println("Cnt: " + cnt.sumThenReset());
}
}
}
).start();
final byte[] payload = new byte[256];
for (int i = 0; i < 4; i++) {
new Thread(
new Runnable() {
@Override
public void run() {
ThreadLocalRandom rnd = ThreadLocalRandom.current();
for (;;) {
Transaction tx = ignite.transactions()
.txStart(TransactionConcurrency.PESSIMISTIC,
TransactionIsolation.REPEATABLE_READ);
replCache.put(rnd.nextInt(100_000), payload);
tx.commit();
//try {
//Thread.sleep(2000);
//}
//catch (InterruptedException e) {
//e.printStackTrace();
//}
cnt.increment();
}
}
}
).start();
}
}
static IgniteConfiguration config() {
IgniteConfiguration c = new IgniteConfiguration();
c.setGridName("" + System.nanoTime());
c.setLocalHost("127.0.0.1");
TcpCommunicationSpi commSpi = new TcpCommunicationSpi();
commSpi.setSharedMemoryPort(-1);
commSpi.setSelectorsCount(3);
c.setCommunicationSpi(commSpi);
c.setStripedPoolSize(2);
c.setSystemThreadPoolSize(2);
c.setPublicThreadPoolSize(2);
return c;
}
}
{noformat}
> Replicated cache performance degradation.
> -
>
> Key: IGNITE-5293
>
[jira] [Commented] (IGNITE-5263) ODBC: use schema notion instead of cache name
[ https://issues.apache.org/jira/browse/IGNITE-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034839#comment-16034839 ] Igor Sapego commented on IGNITE-5263: - [~vozerov], take a look please. On hold until the issue is resolved somehow. > ODBC: use schema notion instead of cache name > - > > Key: IGNITE-5263 > URL: https://issues.apache.org/jira/browse/IGNITE-5263 > Project: Ignite > Issue Type: Task > Components: odbc, sql >Reporter: Vladimir Ozerov >Assignee: Igor Sapego > Labels: cpp, odbc > Fix For: 2.1 > > > We should no longer operate on "cacheName". Instead, we should work with > schemas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5293) Replicated cache performance degradation.
[
https://issues.apache.org/jira/browse/IGNITE-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034837#comment-16034837
]
ASF GitHub Bot commented on IGNITE-5293:
GitHub user yzhdanov opened a pull request:
https://github.com/apache/ignite/pull/2070
Replicated optimizations
https://issues.apache.org/jira/browse/IGNITE-5293
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yzhdanov/ignite replicated-optimizations
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2070.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 #2070
commit 87708161edac26caa6b6cad0c41fbf40e09aac00
Author: Yakov Zhdanov
Date: 2017-06-01T17:01:58Z
Fixed DiscoverySpi methods return types.
commit 87a79f1fd4c59ba7eb4deba7a83a0b88f50a03f5
Author: Yakov Zhdanov
Date: 2017-06-01T17:15:51Z
wip
commit dd1310f664194d9948eac5a6483e71163821746a
Author: Yakov Zhdanov
Date: 2017-06-02T14:27:05Z
wip
> Replicated cache performance degradation.
> -
>
> Key: IGNITE-5293
> URL: https://issues.apache.org/jira/browse/IGNITE-5293
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Alexei Scherbakov
> Fix For: 2.2
>
>
> With increase in number of nodes puts to replicated cache are slowed down
> almost in the same proportion.
> Unit test reproducer:
> {noformat}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one or more
> * contributor license agreements. See the NOTICE file distributed with
> * this work for additional information regarding copyright ownership.
> * The ASF licenses this file to You under the Apache License, Version 2.0
> * (the "License"); you may not use this file except in compliance with
> * the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.ignite.internal.processors.cache.distributed.replicated;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.MemoryConfiguration;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> /**
> * Tests replicated cache performance .
> */
> public class GridCacheReplicatedTransactionalDegradationTest extends
> GridCommonAbstractTest {
> /** Keys. */
> private static final int KEYS = 100_000;
> @Override protected IgniteConfiguration getConfiguration(String gridName)
> throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(gridName);
> cfg.setClientMode(gridName.startsWith("client"));
> CacheConfiguration ccfg = new CacheConfiguration();
> ccfg.setCacheMode(CacheMode.REPLICATED);
> ccfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
>
> ccfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
> ccfg.setName("test");
> cfg.setCacheConfiguration(ccfg);
> return cfg;
> }
> /** */
> public void testThroughput() throws Exception {
> try {
> IgniteEx grid0 = startGrid(0);
> Ignite client = startGrid("client");
> IgniteCache cache =
> client.getOrCreateCache("test");
> doTest(client, cache);
> startGrid(1);
> doTest(client, cache);
> startGrid(2);
> doTest(client, cache);
> } finally {
> stopAllGrids();
> }
> }
> /**
> * @param client
> * @param cache Cache.
> */
> private void doTest(Ignite client, IgniteCache cache) {
> long t1 = System.currentTimeMillis();
> for (int i = 0; i < KE
[jira] [Commented] (IGNITE-5255) JDBC Driver: support DML
[ https://issues.apache.org/jira/browse/IGNITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034835#comment-16034835 ] ASF GitHub Bot commented on IGNITE-5255: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2068 > JDBC Driver: support DML > - > > Key: IGNITE-5255 > URL: https://issues.apache.org/jira/browse/IGNITE-5255 > Project: Ignite > Issue Type: Task > Components: odbc, sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5283) Transaction recovery works incorrectly with cache store and writeThrough enabled
[
https://issues.apache.org/jira/browse/IGNITE-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034825#comment-16034825
]
Andrey Gura commented on IGNITE-5283:
-
Need to port to 2.0
> Transaction recovery works incorrectly with cache store and writeThrough
> enabled
>
>
> Key: IGNITE-5283
> URL: https://issues.apache.org/jira/browse/IGNITE-5283
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> Transaction (at least optimistic) recovery on backups works incorrectly when
> cache store and writeThrough enabled. Changes aren't propagated to DB (it's
> correct) but propagated to cache if primary node left topology.
> It happens because {{IgniteTxRemoteStateAdapter.storeUsed()}} method always
> returns {{false}}. As result incorrect code branch executes in
> {{NodeFailureTimeoutObject.onTimeout0()}} method ({{salvageTx()}} method
> should be invoked).
> *Steps to reproduce*:
> - Start two nodes A and B with cache. Cache store and writeThrough are anbled.
> - From node A start optimistic transaction which executes put/update
> operation for key. Node A should be primary for this key.
> - Kill node A when {{CacheStore.sessionEnd()}} method is invoked but changes
> are not propagated to underlying database (before commit on connection).
> - DB doesn't contain changes but node B contains it.
> *Expected behaviour:*
> All changes should be rolled back.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5237) JDBC thin driver: support client info
[ https://issues.apache.org/jira/browse/IGNITE-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5237: Summary: JDBC thin driver: support client info (was: JDBC Driver: support client info) > JDBC thin driver: support client info > - > > Key: IGNITE-5237 > URL: https://issues.apache.org/jira/browse/IGNITE-5237 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5237) JDBC Driver: support client info
[ https://issues.apache.org/jira/browse/IGNITE-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5237: Fix Version/s: (was: 2.1) 2.2 > JDBC Driver: support client info > > > Key: IGNITE-5237 > URL: https://issues.apache.org/jira/browse/IGNITE-5237 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5400) Migrate new SQL configuration to .NET
Vladimir Ozerov created IGNITE-5400: --- Summary: Migrate new SQL configuration to .NET Key: IGNITE-5400 URL: https://issues.apache.org/jira/browse/IGNITE-5400 Project: Ignite Issue Type: Task Components: platforms, sql Reporter: Vladimir Ozerov Fix For: 2.1 We should move new SQL server configuration to .NET once IGNITE-5275 is ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5399) Manual cache rebalancing feature is broken
[ https://issues.apache.org/jira/browse/IGNITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-5399: - Priority: Critical (was: Major) > Manual cache rebalancing feature is broken > -- > > Key: IGNITE-5399 > URL: https://issues.apache.org/jira/browse/IGNITE-5399 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.8, 1.9, 2.0 >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.2 > > Attachments: ManualRebalanceBug.java > > > Cache.rebalance() javadoc says "Future that will be completed when > rebalancing is finished". But it is not true. > 1. The method return value is Object, however actually it is Boolean and it > is not obvious. > 2. Future.get() return true if rebalance is finished, but can return false > and reschedule rebalancing. So, control can return to thread before > rebalancing even started. > 3. Spinning on rebalance().get() until it true will not help. Seems like > rebalance either restarted (1.9) or hanged (2.0). > PFA repro attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5399) Manual cache rebalancing feature is broken
[ https://issues.apache.org/jira/browse/IGNITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-5399: - Attachment: ManualRebalanceBug.java > Manual cache rebalancing feature is broken > -- > > Key: IGNITE-5399 > URL: https://issues.apache.org/jira/browse/IGNITE-5399 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.8, 1.9, 2.0 >Reporter: Andrew Mashenkov > Fix For: 2.2 > > Attachments: ManualRebalanceBug.java > > > Cache.rebalance() javadoc says "Future that will be completed when > rebalancing is finished". But it is not true. > 1. The method return value is Object, however actually it is Boolean and it > is not obvious. > 2. Future.get() return true if rebalance is finished, but can return false > and reschedule rebalancing. So, control can return to thread before > rebalancing even started. > 3. Spinning on rebalance().get() until it true will not help. Seems like > rebalance either restarted (1.9) or hanged (2.0). > PFA repro attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-5393) .NET: NuGet suite fails on TC
[ https://issues.apache.org/jira/browse/IGNITE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-5393. Resolution: Fixed > .NET: NuGet suite fails on TC > - > > Key: IGNITE-5393 > URL: https://issues.apache.org/jira/browse/IGNITE-5393 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > > IGNITE-5365 changed the build procedure and JAR files are in a different > place now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5393) .NET: NuGet suite fails on TC
[ https://issues.apache.org/jira/browse/IGNITE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034804#comment-16034804 ] ASF GitHub Bot commented on IGNITE-5393: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2069 > .NET: NuGet suite fails on TC > - > > Key: IGNITE-5393 > URL: https://issues.apache.org/jira/browse/IGNITE-5393 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > > IGNITE-5365 changed the build procedure and JAR files are in a different > place now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-5393) .NET: NuGet suite fails on TC
[
https://issues.apache.org/jira/browse/IGNITE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034787#comment-16034787
]
Pavel Tupitsyn edited comment on IGNITE-5393 at 6/2/17 2:43 PM:
Refactored the build procedure to use build script; fixed the build script to
copy jars properly.
Merged to master: {{4024cd3a3e2c3c9cd41a16018a15aaf8b0e3daad}}
was (Author: ptupitsyn):
Refactored the build procedure to use build script; fixed the build script to
copy jars properly.
> .NET: NuGet suite fails on TC
> -
>
> Key: IGNITE-5393
> URL: https://issues.apache.org/jira/browse/IGNITE-5393
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> IGNITE-5365 changed the build procedure and JAR files are in a different
> place now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5327) Create predefined cache templates for CREATE TABLE command
[
https://issues.apache.org/jira/browse/IGNITE-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034801#comment-16034801
]
ASF GitHub Bot commented on IGNITE-5327:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2056
> Create predefined cache templates for CREATE TABLE command
> --
>
> Key: IGNITE-5327
> URL: https://issues.apache.org/jira/browse/IGNITE-5327
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> We need to add predefined templates which will always be available on the
> node. Let's avoid adding them to node configuration to avoid cache data
> sharing on node startup. Instead, let's just create them on-fly when certain
> template name is found.
> Proposed templates:
> 1) "PARTITIONED" => {{new CacheConfiguration().setCacheMode(PARTITIONED)}}
> 2) "REPLICATED" => {{new CacheConfiguration().setCacheMode(REPLICATED)}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-3562) Dependency to outdated Lucene 3.5.0
[
https://issues.apache.org/jira/browse/IGNITE-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034799#comment-16034799
]
Pavel Tupitsyn commented on IGNITE-3562:
Investigated failures in .NET with latest master.
* Each test does {{cache.Clear()}} in the teardown
* One of the previous tests puts 2 items into cache
* {{TestTextQuery}} observes data from previous test even though
{{cache.IsEmpty}} is true
It seems like Lucene index is not cleared on {{cache.Clear()}}. We should add a
test in Java to reproduce the problem first of all.
> Dependency to outdated Lucene 3.5.0
> ---
>
> Key: IGNITE-3562
> URL: https://issues.apache.org/jira/browse/IGNITE-3562
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
>Reporter: Alexander Veit
>Assignee: Andrew Mashenkov
> Labels: important
> Fix For: 2.1
>
>
> Ignite 1.6.0 comes with Lucene 3.5.0 core as dependency, which dates back to
> the year 2011.
> This makes it difficult to integrate with newer software.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-5327) Create predefined cache templates for CREATE TABLE command
[
https://issues.apache.org/jira/browse/IGNITE-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-5327.
-
Resolution: Fixed
> Create predefined cache templates for CREATE TABLE command
> --
>
> Key: IGNITE-5327
> URL: https://issues.apache.org/jira/browse/IGNITE-5327
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> We need to add predefined templates which will always be available on the
> node. Let's avoid adding them to node configuration to avoid cache data
> sharing on node startup. Instead, let's just create them on-fly when certain
> template name is found.
> Proposed templates:
> 1) "PARTITIONED" => {{new CacheConfiguration().setCacheMode(PARTITIONED)}}
> 2) "REPLICATED" => {{new CacheConfiguration().setCacheMode(REPLICATED)}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5255) JDBC Driver: support DML
[ https://issues.apache.org/jira/browse/IGNITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034792#comment-16034792 ] Taras Ledkov commented on IGNITE-5255: -- Fixed. [Tests results|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2068%2Fhead] are OK with me. [~vozerov], please review the changes. > JDBC Driver: support DML > - > > Key: IGNITE-5255 > URL: https://issues.apache.org/jira/browse/IGNITE-5255 > Project: Ignite > Issue Type: Task > Components: odbc, sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-1553) Optimize transaction prepare step when store is enabled
[
https://issues.apache.org/jira/browse/IGNITE-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-1553:
Assignee: Alexey Kuznetsov
> Optimize transaction prepare step when store is enabled
> ---
>
> Key: IGNITE-1553
> URL: https://issues.apache.org/jira/browse/IGNITE-1553
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Labels: important
>
> Currently entries are enlisted in a database transaction after grid
> transaction is in PREPARED state. We can do this in parallel in the following
> fashion (pseudo-code):
> {code}
> fut = tx.prepareAsync();
> db.write(tx.writes());
> fut.get();
> try {
> db.commit();
>
> tx.commit();
> }
> catch (Exception e) {
> tx.rollback();
> }
> {code}
> If this approach is applied, we should be able to reduce latency for
> transactions when write-through is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5393) .NET: NuGet suite fails on TC
[ https://issues.apache.org/jira/browse/IGNITE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034787#comment-16034787 ] Pavel Tupitsyn commented on IGNITE-5393: Refactored the build procedure to use build script; fixed the build script to copy jars properly. > .NET: NuGet suite fails on TC > - > > Key: IGNITE-5393 > URL: https://issues.apache.org/jira/browse/IGNITE-5393 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > > IGNITE-5365 changed the build procedure and JAR files are in a different > place now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5399) Manual cache rebalancing feature is broken
Andrew Mashenkov created IGNITE-5399: Summary: Manual cache rebalancing feature is broken Key: IGNITE-5399 URL: https://issues.apache.org/jira/browse/IGNITE-5399 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.0, 1.9, 1.8 Reporter: Andrew Mashenkov Fix For: 2.2 Cache.rebalance() javadoc says "Future that will be completed when rebalancing is finished". But it is not true. 1. The method return value is Object, however actually it is Boolean and it is not obvious. 2. Future.get() return true if rebalance is finished, but can return false and reschedule rebalancing. So, control can return to thread before rebalancing even started. 3. Spinning on rebalance().get() until it true will not help. Seems like rebalance either restarted (1.9) or hanged (2.0). PFA repro attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4892) Support DML for old (deprecated) thin client based JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4892: Summary: Support DML for old (deprecated) thin client based JDBC driver (was: Support DML for thin client based JDBC driver) > Support DML for old (deprecated) thin client based JDBC driver > -- > > Key: IGNITE-4892 > URL: https://issues.apache.org/jira/browse/IGNITE-4892 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Denis Magda >Assignee: Taras Ledkov > Fix For: 2.1 > > > Support all DML operations for the thin client based JDBC driver: > https://apacheignite.readme.io/docs/jdbc-driver#hostname-based-jdbc-connection -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5249) The release build procedure
[ https://issues.apache.org/jira/browse/IGNITE-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034762#comment-16034762 ] Oleg Ostanin commented on IGNITE-5249: -- I'm working on the task to allow Apache community members use build procedure without disclosing their credentials to repositories. > The release build procedure > --- > > Key: IGNITE-5249 > URL: https://issues.apache.org/jira/browse/IGNITE-5249 > Project: Ignite > Issue Type: Task > Components: build >Reporter: Sergey Kozlov >Assignee: Oleg Ostanin > Fix For: 2.1 > > > The release build procedure should be placed on the CI/CD server and > available to run for the release engineer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-5307) Add "schema" property to SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-5307. - Resolution: Fixed > Add "schema" property to SqlFieldsQuery > --- > > Key: IGNITE-5307 > URL: https://issues.apache.org/jira/browse/IGNITE-5307 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 2.1 > > > This way we will be able to execute certain SQL requests without having cache > at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5398) Optimize allocations in RendezvousAffinityFunction
Alexey Goncharuk created IGNITE-5398:
Summary: Optimize allocations in RendezvousAffinityFunction
Key: IGNITE-5398
URL: https://issues.apache.org/jira/browse/IGNITE-5398
Project: Ignite
Issue Type: Improvement
Components: cache
Affects Versions: 2.0
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Fix For: 2.1
Currently {{RendezvousAffinityFunction}} allocates a new array of tuples (Long,
ClusterNode) in order to create a sorted structure for the partition
assignment. This structure is allocated for each cache and each partition,
which leads to excessive GC pressure during partition map exchange.
I suggest we create a special container which is allocated once per context and
reused for all partition assignments. This container can be reused efficiently
for all caches because it's size is equal to the number of nodes in the
assignment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5360) Validate SQL configuration state from discovery thread
[
https://issues.apache.org/jira/browse/IGNITE-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5360:
Fix Version/s: (was: 2.1)
> Validate SQL configuration state from discovery thread
> --
>
> Key: IGNITE-5360
> URL: https://issues.apache.org/jira/browse/IGNITE-5360
> Project: Ignite
> Issue Type: Task
> Components: cache, sql
>Reporter: Vladimir Ozerov
>
> If started cache belongs to shared schema, we may receive exception due to
> duplicate objects (tables, indexes) in exchange thread, thus causing a hang.
> Need to implement additional validation in discovery thread when it is safe
> to fail.
> See {{SqlPublicSchemaSelfTest#_testTypeConflictInPublicSchema}} as an example
> of failing test.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-5360) Validate SQL configuration state from discovery thread
[
https://issues.apache.org/jira/browse/IGNITE-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-5360.
-
Resolution: Duplicate
> Validate SQL configuration state from discovery thread
> --
>
> Key: IGNITE-5360
> URL: https://issues.apache.org/jira/browse/IGNITE-5360
> Project: Ignite
> Issue Type: Task
> Components: cache, sql
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> If started cache belongs to shared schema, we may receive exception due to
> duplicate objects (tables, indexes) in exchange thread, thus causing a hang.
> Need to implement additional validation in discovery thread when it is safe
> to fail.
> See {{SqlPublicSchemaSelfTest#_testTypeConflictInPublicSchema}} as an example
> of failing test.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (IGNITE-5360) Validate SQL configuration state from discovery thread
[
https://issues.apache.org/jira/browse/IGNITE-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-5360.
---
> Validate SQL configuration state from discovery thread
> --
>
> Key: IGNITE-5360
> URL: https://issues.apache.org/jira/browse/IGNITE-5360
> Project: Ignite
> Issue Type: Task
> Components: cache, sql
>Reporter: Vladimir Ozerov
>
> If started cache belongs to shared schema, we may receive exception due to
> duplicate objects (tables, indexes) in exchange thread, thus causing a hang.
> Need to implement additional validation in discovery thread when it is safe
> to fail.
> See {{SqlPublicSchemaSelfTest#_testTypeConflictInPublicSchema}} as an example
> of failing test.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5397) JDBC thin driver: clear server cursor automatically when last result piece is transmitted
[ https://issues.apache.org/jira/browse/IGNITE-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5397: Labels: performance (was: important performance) > JDBC thin driver: clear server cursor automatically when last result piece is > transmitted > - > > Key: IGNITE-5397 > URL: https://issues.apache.org/jira/browse/IGNITE-5397 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov > Labels: performance > Fix For: 2.1 > > > When last part of result set is sent from the server, we should do the > following: > 1) Clear server-side cursor > 2) Set special marker on the client side that "cursor" close request is not > needed. This way we will save two network hops for typical DML request. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5397) JDBC thin driver: clear server cursor automatically when last result piece is transmitted
Vladimir Ozerov created IGNITE-5397: --- Summary: JDBC thin driver: clear server cursor automatically when last result piece is transmitted Key: IGNITE-5397 URL: https://issues.apache.org/jira/browse/IGNITE-5397 Project: Ignite Issue Type: Task Components: sql Affects Versions: 2.0 Reporter: Vladimir Ozerov Assignee: Taras Ledkov Fix For: 2.1 When last part of result set is sent from the server, we should do the following: 1) Clear server-side cursor 2) Set special marker on the client side that "cursor" close request is not needed. This way we will save two network hops for typical DML request. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5396) ODBC: Clear server cursor automatically when last result piece is transmitted
Vladimir Ozerov created IGNITE-5396: --- Summary: ODBC: Clear server cursor automatically when last result piece is transmitted Key: IGNITE-5396 URL: https://issues.apache.org/jira/browse/IGNITE-5396 Project: Ignite Issue Type: Task Components: odbc Affects Versions: 2.0 Reporter: Vladimir Ozerov Assignee: Igor Sapego Fix For: 2.1 When last part of result set is sent from the server, we should do the following: 1) Clear server-side cursor 2) Set special marker on the client side that "cursor" close request is not needed. This way we will save two network hops for typical DML request. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4370) ODBC: Implement DML operations with parameters in batch.
[
https://issues.apache.org/jira/browse/IGNITE-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4370:
Labels: important (was: odbc)
> ODBC: Implement DML operations with parameters in batch.
>
>
> Key: IGNITE-4370
> URL: https://issues.apache.org/jira/browse/IGNITE-4370
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: important
> Fix For: 2.1
>
>
> Currently, if user wants for example to insert 20k records they need to call
> {{SQLExecute}} for the 20k times. More than that, internally, we transmit and
> execute the same SQL query 20k times. This is a huge overhead. We should only
> transfer sql query once, transfer all the parameters in a batch and then
> execute it once using some fast, possibly internal API.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4370) ODBC: Implement DML operations with parameters in batch.
[
https://issues.apache.org/jira/browse/IGNITE-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego reassigned IGNITE-4370:
---
Assignee: Igor Sapego
> ODBC: Implement DML operations with parameters in batch.
>
>
> Key: IGNITE-4370
> URL: https://issues.apache.org/jira/browse/IGNITE-4370
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: odbc
> Fix For: 2.1
>
>
> Currently, if user wants for example to insert 20k records they need to call
> {{SQLExecute}} for the 20k times. More than that, internally, we transmit and
> execute the same SQL query 20k times. This is a huge overhead. We should only
> transfer sql query once, transfer all the parameters in a batch and then
> execute it once using some fast, possibly internal API.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5395) Move ignite-ps module to ignite-core
Alexey Goncharuk created IGNITE-5395: Summary: Move ignite-ps module to ignite-core Key: IGNITE-5395 URL: https://issues.apache.org/jira/browse/IGNITE-5395 Project: Ignite Issue Type: Sub-task Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5394) Cache-independent SQL query fails if no tables are present in it
Vladimir Ozerov created IGNITE-5394:
---
Summary: Cache-independent SQL query fails if no tables are
present in it
Key: IGNITE-5394
URL: https://issues.apache.org/jira/browse/IGNITE-5394
Project: Ignite
Issue Type: Task
Components: sql
Reporter: Vladimir Ozerov
Fix For: 2.1
Sample query:
{code}
SELECT CURRENT_DATE()
{code}
Looks like we should just execute this query locally against specified schema.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5267) Persistent storage migration
[ https://issues.apache.org/jira/browse/IGNITE-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5267: Labels: important (was: ) > Persistent storage migration > > > Key: IGNITE-5267 > URL: https://issues.apache.org/jira/browse/IGNITE-5267 > Project: Ignite > Issue Type: New Feature > Components: cache >Affects Versions: 2.0 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk > Labels: important > Fix For: 2.1 > > > The ticket for the GridGain persistent store migration process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-3735) ODBC: Support escape sequences.
[ https://issues.apache.org/jira/browse/IGNITE-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-3735. - Resolution: Fixed > ODBC: Support escape sequences. > --- > > Key: IGNITE-3735 > URL: https://issues.apache.org/jira/browse/IGNITE-3735 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.7 >Reporter: Vladimir Ozerov > Fix For: 2.1 > > > Our driver must support standard ODBC escape sequences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034659#comment-16034659 ] ASF GitHub Bot commented on IGNITE-5355: Github user achetaev closed the pull request at: https://github.com/apache/ignite/pull/2064 > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev > > 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5255) JDBC Driver: support DML
[
https://issues.apache.org/jira/browse/IGNITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034650#comment-16034650
]
Vladimir Ozerov commented on IGNITE-5255:
-
[~tledkov-gridgain], looks good to me, except of {{args}} being located in
{{JdbcPreparedStatement}}. Let's move them to {{JdbcThinPreparedStatement}}
instead.
> JDBC Driver: support DML
> -
>
> Key: IGNITE-5255
> URL: https://issues.apache.org/jira/browse/IGNITE-5255
> Project: Ignite
> Issue Type: Task
> Components: odbc, sql
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5393) .NET: NuGet suite fails on TC
[ https://issues.apache.org/jira/browse/IGNITE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034642#comment-16034642 ] ASF GitHub Bot commented on IGNITE-5393: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2069 IGNITE-5393 .NET: Fix NuGet suite build You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-5393 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2069.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 #2069 commit a48154cc489137bd8a0c980c17f08263c5eeacc9 Author: Pavel Tupitsyn Date: 2017-06-02T12:30:40Z Fix jar copy script commit 7e978ddf0dd3c98899a5bd589bcb0bcafc1b1980 Author: Pavel Tupitsyn Date: 2017-06-02T12:34:14Z wip commit 9568837d656c0b73932fdccb6d2f3f5bce356b0f Author: Pavel Tupitsyn Date: 2017-06-02T12:42:53Z Fixing nuget tests to use common build script commit d7367d1fcbd1092bf3b9c66f86f3958d53f4bd1e Author: Pavel Tupitsyn Date: 2017-06-02T12:46:42Z Fixing nuget tests to use common build script commit ddcb8f143785d790f86e87ee2440c91a25007a76 Author: Pavel Tupitsyn Date: 2017-06-02T12:59:45Z wip > .NET: NuGet suite fails on TC > - > > Key: IGNITE-5393 > URL: https://issues.apache.org/jira/browse/IGNITE-5393 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > > IGNITE-5365 changed the build procedure and JAR files are in a different > place now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5255) JDBC Driver: support DML
[ https://issues.apache.org/jira/browse/IGNITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034614#comment-16034614 ] Taras Ledkov commented on IGNITE-5255: -- [~vozerov], please review the patch. > JDBC Driver: support DML > - > > Key: IGNITE-5255 > URL: https://issues.apache.org/jira/browse/IGNITE-5255 > Project: Ignite > Issue Type: Task > Components: odbc, sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-5255) JDBC Driver: support DML
[ https://issues.apache.org/jira/browse/IGNITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034473#comment-16034473 ] Taras Ledkov edited comment on IGNITE-5255 at 6/2/17 12:30 PM: --- Waits for [tests results|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2068%2Fhead] was (Author: tledkov-gridgain): [Tests results|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2050%2Fhead] > JDBC Driver: support DML > - > > Key: IGNITE-5255 > URL: https://issues.apache.org/jira/browse/IGNITE-5255 > Project: Ignite > Issue Type: Task > Components: odbc, sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5255) JDBC Driver: support DML
[ https://issues.apache.org/jira/browse/IGNITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034611#comment-16034611 ] ASF GitHub Bot commented on IGNITE-5255: GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2068 IGNITE-5255: implement update methods for jdbc statements You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5255 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2068.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 #2068 commit 91dc6959d2d9eaa411dc95c20f71ebbfefffcd4d Author: tledkov-gridgain Date: 2017-06-02T12:17:46Z IGNITE-5255: implement update methods for jdbc statements > JDBC Driver: support DML > - > > Key: IGNITE-5255 > URL: https://issues.apache.org/jira/browse/IGNITE-5255 > Project: Ignite > Issue Type: Task > Components: odbc, sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5328) Support cache atomicity mode for CREATE TABLE
[
https://issues.apache.org/jira/browse/IGNITE-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034610#comment-16034610
]
ASF GitHub Bot commented on IGNITE-5328:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2054
> Support cache atomicity mode for CREATE TABLE
> -
>
> Key: IGNITE-5328
> URL: https://issues.apache.org/jira/browse/IGNITE-5328
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> Users should be able to set atomicity mode through "WITH" synthax.
> Property name: {{atomicityMode}}
> Allowed values (case insensitive): {{atomic}}, {{transactional}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5393) .NET: NuGet suite fails on TC
Pavel Tupitsyn created IGNITE-5393: -- Summary: .NET: NuGet suite fails on TC Key: IGNITE-5393 URL: https://issues.apache.org/jira/browse/IGNITE-5393 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 2.1 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.1 IGNITE-5365 changed the build procedure and JAR files are in a different place now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5263) ODBC: use schema notion instead of cache name
[
https://issues.apache.org/jira/browse/IGNITE-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034604#comment-16034604
]
Igor Sapego commented on IGNITE-5263:
-
Getting exceptions when trying to execute queries for no particular cache:
{noformat}
Failed to find at least one cache for SQL statement: SELECT CURRENT_DATE()
{noformat}
> ODBC: use schema notion instead of cache name
> -
>
> Key: IGNITE-5263
> URL: https://issues.apache.org/jira/browse/IGNITE-5263
> Project: Ignite
> Issue Type: Task
> Components: odbc, sql
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
> Labels: cpp, odbc
> Fix For: 2.1
>
>
> We should no longer operate on "cacheName". Instead, we should work with
> schemas.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5255) JDBC Driver: support DML
[ https://issues.apache.org/jira/browse/IGNITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034598#comment-16034598 ] ASF GitHub Bot commented on IGNITE-5255: Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/2050 > JDBC Driver: support DML > - > > Key: IGNITE-5255 > URL: https://issues.apache.org/jira/browse/IGNITE-5255 > Project: Ignite > Issue Type: Task > Components: odbc, sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (IGNITE-4908) Ignite.reentrantLock looks much slower than IgniteCache.lock.
[ https://issues.apache.org/jira/browse/IGNITE-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Menshikov updated IGNITE-4908: Comment: was deleted (was: [~amashenkov] , I was busy by working on IGNITE-4501. Looks like this week is my last chance to make it. If I fail, I will return to this task. If it's too late, it's better to reassign this task.) > Ignite.reentrantLock looks much slower than IgniteCache.lock. > - > > Key: IGNITE-4908 > URL: https://issues.apache.org/jira/browse/IGNITE-4908 > Project: Ignite > Issue Type: Improvement > Components: data structures >Affects Versions: 1.8 >Reporter: Andrew Mashenkov >Assignee: Alexander Menshikov > Fix For: 2.1 > > > We should make a benchmark and investigate this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5305) DDL: Set schema to cache configuration during CREATE TABLE
[
https://issues.apache.org/jira/browse/IGNITE-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034560#comment-16034560
]
ASF GitHub Bot commented on IGNITE-5305:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2055
> DDL: Set schema to cache configuration during CREATE TABLE
> --
>
> Key: IGNITE-5305
> URL: https://issues.apache.org/jira/browse/IGNITE-5305
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> See {{GridQueryProcessor.dynamicTableCreate}} method. We have unused
> parameter {{schemaName}}. It should be set to
> {{CacheConfiguration.sqlSchema}}.
> If I try to do so, {{H2DynamicTableTest}} start to hang due to exception in
> exchange thread due to some error in indexing engine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5176) JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol
[ https://issues.apache.org/jira/browse/IGNITE-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034538#comment-16034538 ] ASF GitHub Bot commented on IGNITE-5176: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2040 > JDBC Driver: implement query execution for thin jdbc driver based on common > odbc/jdbc protocol > -- > > Key: IGNITE-5176 > URL: https://issues.apache.org/jira/browse/IGNITE-5176 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > > Implementation query execution & fetch results for thin JDBC driver over ODBC > protocol. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5335) Wrong value read by SQL query for field containing negative decimal
[ https://issues.apache.org/jira/browse/IGNITE-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034532#comment-16034532 ] ASF GitHub Bot commented on IGNITE-5335: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2034 > Wrong value read by SQL query for field containing negative decimal > --- > > Key: IGNITE-5335 > URL: https://issues.apache.org/jira/browse/IGNITE-5335 > Project: Ignite > Issue Type: Bug > Components: binary, sql >Affects Versions: 2.0 >Reporter: Sergey Kalashnikov >Assignee: Sergey Kalashnikov > Labels: important > Fix For: 2.1 > > Attachments: BinaryObjectFieldDecimalTest.java > > > Steps to reproduce: > 1) Create a cache with value type having some decimal field. > 2) Instantiate a value, intialize decimal field with a negative value and put > it to the cache. > 3) Perform an sql query on the decimal field. > 4) Check the selected value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5113) K-means clustering
[ https://issues.apache.org/jira/browse/IGNITE-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak reassigned IGNITE-5113: -- Assignee: Yury Babak (was: Artem Malykh) > K-means clustering > -- > > Key: IGNITE-5113 > URL: https://issues.apache.org/jira/browse/IGNITE-5113 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Yury Babak > Labels: important > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4509) SQL: query with condition on affinity columns and without joins and subqueries should go to affinity node only
[
https://issues.apache.org/jira/browse/IGNITE-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034521#comment-16034521
]
ASF GitHub Bot commented on IGNITE-4509:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1916
> SQL: query with condition on affinity columns and without joins and
> subqueries should go to affinity node only
> --
>
> Key: IGNITE-4509
> URL: https://issues.apache.org/jira/browse/IGNITE-4509
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
> Labels: important, performance, sql
> Fix For: 2.1
>
>
> Simple SQL queries usually demonstrate negative scalability when more nodes
> are added.
> Consider the following query:
> {code}
> SELECT * FROM Person p
> WHERE p.id = ?
> {code}
> If {{Person.id}} is affinity field, then query can be replaced with plain
> {{IgniteCache.get}} or some specialized version of GET, which will return
> only desired fields. This optimization will guarantee smooth scale with any
> number of nodes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4937) Transactions deadlock detection should happen on each grid hang
[ https://issues.apache.org/jira/browse/IGNITE-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034513#comment-16034513 ] Anton Vinogradov commented on IGNITE-4937: -- [~avinogradov] Just test comment > Transactions deadlock detection should happen on each grid hang > --- > > Key: IGNITE-4937 > URL: https://issues.apache.org/jira/browse/IGNITE-4937 > Project: Ignite > Issue Type: Task > Components: cache >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Critical > Fix For: 2.1 > > > Each "Failed to wait for partition map exchange" or similar should cause such > check. > Check can be added to > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#dumpPendingObjects > or/and > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#dumpLongRunningOperations -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (IGNITE-4937) Transactions deadlock detection should happen on each grid hang
[ https://issues.apache.org/jira/browse/IGNITE-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-4937: - Comment: was deleted (was: [~avinogradov] Just test comment) > Transactions deadlock detection should happen on each grid hang > --- > > Key: IGNITE-4937 > URL: https://issues.apache.org/jira/browse/IGNITE-4937 > Project: Ignite > Issue Type: Task > Components: cache >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Critical > Fix For: 2.1 > > > Each "Failed to wait for partition map exchange" or similar should cause such > check. > Check can be added to > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#dumpPendingObjects > or/and > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#dumpLongRunningOperations -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5255) JDBC Driver: support DML
[ https://issues.apache.org/jira/browse/IGNITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034473#comment-16034473 ] Taras Ledkov commented on IGNITE-5255: -- [Tests results|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2050%2Fhead] > JDBC Driver: support DML > - > > Key: IGNITE-5255 > URL: https://issues.apache.org/jira/browse/IGNITE-5255 > Project: Ignite > Issue Type: Task > Components: odbc, sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4615) Ignite should be compilable under JDK 9
[ https://issues.apache.org/jira/browse/IGNITE-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev updated IGNITE-4615: -- Fix Version/s: (was: 2.1) 2.2 > Ignite should be compilable under JDK 9 > --- > > Key: IGNITE-4615 > URL: https://issues.apache.org/jira/browse/IGNITE-4615 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Evgenii Zhuravlev > Fix For: 2.2 > > Attachments: ignite.jar.dot > > > The original discussion on the dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/Should-we-take-care-of-Java-9-in-Ignite-2-0-scope-td14018.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-4939) Receive event before cache initialized
[
https://issues.apache.org/jira/browse/IGNITE-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zhuravlev resolved IGNITE-4939.
---
Resolution: Won't Fix
Not reproducible since 2.0
> 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] [Resolved] (IGNITE-4232) "IllegalArgumentException: Cache is not configured: ignite-marshaller-sys-cache" while starting grid
[
https://issues.apache.org/jira/browse/IGNITE-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zhuravlev resolved IGNITE-4232.
---
Resolution: Won't Fix
Not reproducible since 2.0
> "IllegalArgumentException: Cache is not configured:
> ignite-marshaller-sys-cache" while starting grid
>
>
> Key: IGNITE-4232
> URL: https://issues.apache.org/jira/browse/IGNITE-4232
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Ksenia Rybakova
>Assignee: Evgenii Zhuravlev
> Fix For: 2.1
>
>
> While starting a grid with 20 servers and 5 clients the follwing errors occur
> at some drivers:
> {noformat}
> [12:16:55,985][INFO ][main][IgniteKernal] Language runtime: Java Platform API
> Specification ver. 1.7
> [12:16:55,985][INFO ][main][IgniteKernal] VM information: Java(TM) SE Runtime
> Environment 1.7.0_79-b15 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM
> 24.79-b02
> [12:16:55,986][INFO ][main][IgniteKernal] VM total memory: 4.0GB
> [12:16:55,986][INFO ][main][IgniteKernal] Remote Management [restart: off,
> REST: on, JMX (remote: off)]
> [12:16:55,986][INFO ][main][IgniteKernal]
> IGNITE_HOME=/home/krybakova/opts-set-w-300-d-3600-m-client-rev-6e36a795-date-1611-121630/yardstick
> [12:16:55,986][INFO ][main][IgniteKernal] VM arguments: [-Xms2g, -Xmx2g,
> -Djava.net.preferIPv4Stack=true, -DIGNITE_QUIET=false, -XX:+UseTLAB,
> -XX:NewSize=512m, -XX:MaxNewSize=512m, -XX:SurvivorRatio=6,
> -XX:+AlwaysPreTouch, -XX:+UseG1GC,
> [12:16:55,986][INFO ][main][IgniteKernal] Configured caches
> ['ignite-marshaller-sys-cache', 'ignite-sys-cache',
> 'ignite-atomics-sys-cache', 'atomic']
> [12:16:55,990][INFO ][main][IgniteKernal] 3-rd party licenses can be found
> at:
> /home/krybakova/opts-set-w-300-d-3600-m-client-rev-6e36a795-date-1611-121630/yardstick/libs/licenses
> [12:16:56,061][INFO ][main][IgnitePluginProcessor] Configured plugins:
> [12:16:56,061][INFO ][main][IgnitePluginProcessor] ^-- None
> [12:16:56,062][INFO ][main][IgnitePluginProcessor]
> [12:16:56,108][INFO ][main][TcpCommunicationSpi] Successfully bound to TCP
> port [port=47104, locHost=0.0.0.0/0.0.0.0]
> [12:16:56,124][WARN ][main][NoopCheckpointSpi] Checkpoints are disabled (to
> enable configure any GridCheckpointSpi implementation)
> [12:16:56,152][WARN ][main][GridCollisionManager] Collision resolution is
> disabled (all jobs will be activated upon arrival).
> [12:16:56,155][WARN ][main][NoopSwapSpaceSpi] Swap space is disabled. To
> enable use FileSwapSpaceSpi.
> [12:16:56,157][INFO ][main][IgniteKernal] Security status
> [authentication=off, tls/ssl=off]
> [12:16:56,408][INFO ][main][GridTcpRestProtocol] Command protocol
> successfully started [name=TCP binary, host=0.0.0.0/0.0.0.0, port=11215]
> [12:16:56,449][INFO ][main][IgniteKernal] Non-loopback local IPs: 172.25.1.34
> [12:16:56,449][INFO ][main][IgniteKernal] Enabled local MACs: 001B21D4F1B8
> Exception in thread "sys-#34%null%" java.lang.IllegalArgumentException: Cache
> is not configured: ignite-marshaller-sys-cache
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:3320)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.handleEvent(CacheContinuousQueryHandler.java:711)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:683)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:642)
> 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:1080)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:101)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2317)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1040)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1900(GridIoManager.java:101)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.
[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=16034441#comment-16034441
]
ASF GitHub Bot commented on IGNITE-4939:
Github user ezhuravl closed the pull request at:
https://github.com/apache/ignite/pull/1814
> 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] [Commented] (IGNITE-5356) .NET: Peer deployment does not load runtime dependencies
[
https://issues.apache.org/jira/browse/IGNITE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034420#comment-16034420
]
ASF GitHub Bot commented on IGNITE-5356:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2063
> .NET: Peer deployment does not load runtime dependencies
>
>
> Key: IGNITE-5356
> URL: https://issues.apache.org/jira/browse/IGNITE-5356
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> Discovered while testing in LINQPad:
> * Start Apache.Ignite.exe with enabled peer loading
> * Run a computation from LINQPad that uses {{Dump}} extension method
> It fails with "Cannot load LINQPad assembly" error, because CLR tries to load
> that assembly during job execution, not during deserialization.
> We should wrap {{ExecuteRemote}} in a {{PeerAssemblyResolver}} to handle
> runtime assembly requests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5356) .NET: Peer deployment does not load runtime dependencies
[
https://issues.apache.org/jira/browse/IGNITE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034415#comment-16034415
]
Pavel Tupitsyn commented on IGNITE-5356:
Merged to master: {{79d45e34335d2286bf382d7a8a49a71661f26f79}}
> .NET: Peer deployment does not load runtime dependencies
>
>
> Key: IGNITE-5356
> URL: https://issues.apache.org/jira/browse/IGNITE-5356
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> Discovered while testing in LINQPad:
> * Start Apache.Ignite.exe with enabled peer loading
> * Run a computation from LINQPad that uses {{Dump}} extension method
> It fails with "Cannot load LINQPad assembly" error, because CLR tries to load
> that assembly during job execution, not during deserialization.
> We should wrap {{ExecuteRemote}} in a {{PeerAssemblyResolver}} to handle
> runtime assembly requests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-5356) .NET: Peer deployment does not load runtime dependencies
[
https://issues.apache.org/jira/browse/IGNITE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-5356.
Resolution: Fixed
> .NET: Peer deployment does not load runtime dependencies
>
>
> Key: IGNITE-5356
> URL: https://issues.apache.org/jira/browse/IGNITE-5356
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> Discovered while testing in LINQPad:
> * Start Apache.Ignite.exe with enabled peer loading
> * Run a computation from LINQPad that uses {{Dump}} extension method
> It fails with "Cannot load LINQPad assembly" error, because CLR tries to load
> that assembly during job execution, not during deserialization.
> We should wrap {{ExecuteRemote}} in a {{PeerAssemblyResolver}} to handle
> runtime assembly requests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5392) Joining node must accept cluster status (active/inactive)
[ https://issues.apache.org/jira/browse/IGNITE-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-5392: --- Component/s: persistence > Joining node must accept cluster status (active/inactive) > - > > Key: IGNITE-5392 > URL: https://issues.apache.org/jira/browse/IGNITE-5392 > Project: Ignite > Issue Type: Task > Components: cache, persistence >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.1 > > > When new node joining in cluster, must accept cluster state (active/inactive) > and perform necessary operations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-5358) .NET: Nullable enum field in binary object causes type cast exception
[
https://issues.apache.org/jira/browse/IGNITE-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-5358.
Resolution: Fixed
> .NET: Nullable enum field in binary object causes type cast exception
> -
>
> Key: IGNITE-5358
> URL: https://issues.apache.org/jira/browse/IGNITE-5358
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.1
>
>
> Reproducer:
> {code}
> enum TestEnum
> {
> TestValue1,
> TestValue2
> };
> class TestClass
> {
> public string Name { get; }
> public TestEnum? EnumValue { get; }
> public TestClass(string name, TestEnum? enumValue)
> {
> Name = name;
> EnumValue = enumValue;
> }
> }
> ...
> cache.Put("TestElem1", new TestClass("TestElem1", TestEnum.TestValue1));
> cache.Get("TestElem1"); // exception
> {code}
> Exception:
> {code}
> No coercion operator is defined between types
> 'Apache.Ignite.Core.Impl.Binary.BinaryEnum' and
> 'System.Nullable`1[UserQuery+TestEnum]'.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5392) Joining node must accept cluster status (active/inactive)
[ https://issues.apache.org/jira/browse/IGNITE-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-5392: --- Summary: Joining node must accept cluster status (active/inactive) (was: Joining node must accept cluster status) > Joining node must accept cluster status (active/inactive) > - > > Key: IGNITE-5392 > URL: https://issues.apache.org/jira/browse/IGNITE-5392 > Project: Ignite > Issue Type: Task > Components: cache >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.1 > > > When new node joining in cluster, must accept cluster state (active/inactive) > and perform necessary operations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5358) .NET: Nullable enum field in binary object causes type cast exception
[
https://issues.apache.org/jira/browse/IGNITE-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034411#comment-16034411
]
Pavel Tupitsyn commented on IGNITE-5358:
TC is good, merged to master: {{34409fd59374a8fad31c592a5517e8d80a032cff}}
> .NET: Nullable enum field in binary object causes type cast exception
> -
>
> Key: IGNITE-5358
> URL: https://issues.apache.org/jira/browse/IGNITE-5358
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.1
>
>
> Reproducer:
> {code}
> enum TestEnum
> {
> TestValue1,
> TestValue2
> };
> class TestClass
> {
> public string Name { get; }
> public TestEnum? EnumValue { get; }
> public TestClass(string name, TestEnum? enumValue)
> {
> Name = name;
> EnumValue = enumValue;
> }
> }
> ...
> cache.Put("TestElem1", new TestClass("TestElem1", TestEnum.TestValue1));
> cache.Get("TestElem1"); // exception
> {code}
> Exception:
> {code}
> No coercion operator is defined between types
> 'Apache.Ignite.Core.Impl.Binary.BinaryEnum' and
> 'System.Nullable`1[UserQuery+TestEnum]'.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5392) Joining node must accept cluster status
Dmitriy Govorukhin created IGNITE-5392: -- Summary: Joining node must accept cluster status Key: IGNITE-5392 URL: https://issues.apache.org/jira/browse/IGNITE-5392 Project: Ignite Issue Type: Task Components: cache Reporter: Dmitriy Govorukhin Assignee: Dmitriy Govorukhin Priority: Critical Fix For: 2.1 When new node joining in cluster, must accept cluster state (active/inactive) and perform necessary operations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5375) New PersistentStoreMetrics, MemoryMetrics interface improvements
[
https://issues.apache.org/jira/browse/IGNITE-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov reassigned IGNITE-5375:
---
Assignee: Sergey Chugunov
> New PersistentStoreMetrics, MemoryMetrics interface improvements
>
>
> Key: IGNITE-5375
> URL: https://issues.apache.org/jira/browse/IGNITE-5375
> Project: Ignite
> Issue Type: Task
> Components: persistence
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Fix For: 2.1
>
>
> h2. Notes
> Original discussions on dev list: on [Persistent Store
> Metrics|http://apache-ignite-developers.2346864.n4.nabble.com/Persistent-Distributed-Store-Metrics-tt17730.html];
> on a new way of thinking of Memory Policies as [virtual
> memory|http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-memory-gt-virtual-memory-tt18291.html].
> Existing {{MemoryMetrics}} interface will be enhanced with additional methods
> for monitoring persistence activities (only new methods are listed):
> {code}
> public interface MemoryMetrics {
> ...
> public long getDirtyPages();
> public float getPagesReplaceRate();
> public long getPhysicalMemoryPages();
> }
> {code}
> Proposed interface for Persistent Store Metrics:
> {code}
> public interface PersistentStoreMetrics {
> public float getWalLoggingRate();
> public int getWalArchiveSegments();
> public float getWalFsyncTime();
> public float getCheckpointingTime();
> public float getCheckpointingFsyncTime();
> public long getCheckpointingTotalPagesNumber();
> public long[] getCheckpointingPagesByTypeNumber();
> public long getCheckpointingCopiedOnWritePagesNumber();
> }
> {code}
> h2. Acceptance Criteria
> # MemoryMetrics interface is expanded with new methods
> # Persistent Store Metrics are implemented according to the proposed interface
> # Semantics of existing method {{MemoryMetrics::getTotalAllocatedPages}} is
> changed to return not only pages residing in memory, but total amount of
> paged including ones on disk.
> For amount of pages in RAM new method {{getPhysicalMemoryPages}} is added.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5358) .NET: Nullable enum field in binary object causes type cast exception
[
https://issues.apache.org/jira/browse/IGNITE-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034410#comment-16034410
]
ASF GitHub Bot commented on IGNITE-5358:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2048
> .NET: Nullable enum field in binary object causes type cast exception
> -
>
> Key: IGNITE-5358
> URL: https://issues.apache.org/jira/browse/IGNITE-5358
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.1
>
>
> Reproducer:
> {code}
> enum TestEnum
> {
> TestValue1,
> TestValue2
> };
> class TestClass
> {
> public string Name { get; }
> public TestEnum? EnumValue { get; }
> public TestClass(string name, TestEnum? enumValue)
> {
> Name = name;
> EnumValue = enumValue;
> }
> }
> ...
> cache.Put("TestElem1", new TestClass("TestElem1", TestEnum.TestValue1));
> cache.Get("TestElem1"); // exception
> {code}
> Exception:
> {code}
> No coercion operator is defined between types
> 'Apache.Ignite.Core.Impl.Binary.BinaryEnum' and
> 'System.Nullable`1[UserQuery+TestEnum]'.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5391) CREATE INDEX and DROP INDEX operations should be allowed back on non-sql caches
[
https://issues.apache.org/jira/browse/IGNITE-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5391:
Fix Version/s: 2.1
> CREATE INDEX and DROP INDEX operations should be allowed back on non-sql
> caches
> ---
>
> Key: IGNITE-5391
> URL: https://issues.apache.org/jira/browse/IGNITE-5391
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Seems there are some cases when this thing could be useful still. E.g. you
> start a cache with some {{QueryEntity}} state, but then understand that you
> forgot to add useful index. Currently you will have to restart the cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-5391) CREATE INDEX and DROP INDEX operations should be allowed back on non-sql caches
[
https://issues.apache.org/jira/browse/IGNITE-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-5391.
-
Resolution: Fixed
> CREATE INDEX and DROP INDEX operations should be allowed back on non-sql
> caches
> ---
>
> Key: IGNITE-5391
> URL: https://issues.apache.org/jira/browse/IGNITE-5391
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>
> Seems there are some cases when this thing could be useful still. E.g. you
> start a cache with some {{QueryEntity}} state, but then understand that you
> forgot to add useful index. Currently you will have to restart the cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-5176) JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol
[ https://issues.apache.org/jira/browse/IGNITE-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033057#comment-16033057 ] Taras Ledkov edited comment on IGNITE-5176 at 6/2/17 9:42 AM: -- [~vozerov], the [tests|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2040%2Fhead] are OK with me. was (Author: tledkov-gridgain): [~vozerov], the [tests|http://195.239.208.174/viewLog.html?buildId=642465&tab=buildResultsDiv&buildTypeId=Ignite20Tests_RunAllSql] are OK with me. > JDBC Driver: implement query execution for thin jdbc driver based on common > odbc/jdbc protocol > -- > > Key: IGNITE-5176 > URL: https://issues.apache.org/jira/browse/IGNITE-5176 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > > Implementation query execution & fetch results for thin JDBC driver over ODBC > protocol. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5103) TcpDiscoverySpi ignores maxMissedClientHeartbeats property
[
https://issues.apache.org/jira/browse/IGNITE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Kaigorodov reassigned IGNITE-5103:
-
Assignee: Alexei Kaigorodov
> TcpDiscoverySpi ignores maxMissedClientHeartbeats property
> --
>
> Key: IGNITE-5103
> URL: https://issues.apache.org/jira/browse/IGNITE-5103
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Alexei Kaigorodov
> Fix For: 2.1
>
> Attachments: TcpDiscoveryClientSuspensionSelfTest.java
>
>
> Test scenario is the following:
> * Start one or more servers.
> * Start a client node.
> * Suspend client process using {{-SIGSTOP}} signal.
> * Wait for {{maxMissedClientHeartbeats*heartbeatFrequency}}.
> * Client node is expected to be removed from topology, but server nodes don't
> do that.
> Attached is the unit test reproducing the same by stopping the heartbeat
> sender thread on the client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5391) CREATE INDEX and DROP INDEX operations should be allowed back on non-sql caches
Vladimir Ozerov created IGNITE-5391:
---
Summary: CREATE INDEX and DROP INDEX operations should be allowed
back on non-sql caches
Key: IGNITE-5391
URL: https://issues.apache.org/jira/browse/IGNITE-5391
Project: Ignite
Issue Type: Task
Components: sql
Affects Versions: 2.1
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Seems there are some cases when this thing could be useful still. E.g. you
start a cache with some {{QueryEntity}} state, but then understand that you
forgot to add useful index. Currently you will have to restart the cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5390) But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest
[ https://issues.apache.org/jira/browse/IGNITE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Belyak updated IGNITE-5390: - Environment: (was: 2.0) > But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest > - > > Key: IGNITE-5390 > URL: https://issues.apache.org/jira/browse/IGNITE-5390 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Trivial > Fix For: 2.1 > > > IgniteCacheTxStoreSessionWriteBehindCoalescingTest override > cacheConfiguration method from IgniteCacheStoreSessionWriteBehindAbstractTest > to switch TestStore into TestNonCoalescingStore. > But IgniteCacheStoreSessionWriteBehindAbstractTest.getConfiguration > cacheStoreFactory explicitly set to TestStore for ccfg1. > Need to remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5390) But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest
[ https://issues.apache.org/jira/browse/IGNITE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Belyak updated IGNITE-5390: - Fix Version/s: 2.1 > But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest > - > > Key: IGNITE-5390 > URL: https://issues.apache.org/jira/browse/IGNITE-5390 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Trivial > Fix For: 2.1 > > > IgniteCacheTxStoreSessionWriteBehindCoalescingTest override > cacheConfiguration method from IgniteCacheStoreSessionWriteBehindAbstractTest > to switch TestStore into TestNonCoalescingStore. > But IgniteCacheStoreSessionWriteBehindAbstractTest.getConfiguration > cacheStoreFactory explicitly set to TestStore for ccfg1. > Need to remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5390) But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest
[ https://issues.apache.org/jira/browse/IGNITE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Belyak updated IGNITE-5390: - Affects Version/s: 2.0 > But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest > - > > Key: IGNITE-5390 > URL: https://issues.apache.org/jira/browse/IGNITE-5390 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Trivial > Fix For: 2.1 > > > IgniteCacheTxStoreSessionWriteBehindCoalescingTest override > cacheConfiguration method from IgniteCacheStoreSessionWriteBehindAbstractTest > to switch TestStore into TestNonCoalescingStore. > But IgniteCacheStoreSessionWriteBehindAbstractTest.getConfiguration > cacheStoreFactory explicitly set to TestStore for ccfg1. > Need to remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5390) But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest
[ https://issues.apache.org/jira/browse/IGNITE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Belyak updated IGNITE-5390: - Environment: 2.0 > But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest > - > > Key: IGNITE-5390 > URL: https://issues.apache.org/jira/browse/IGNITE-5390 > Project: Ignite > Issue Type: Bug > Environment: 2.0 >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Trivial > > IgniteCacheTxStoreSessionWriteBehindCoalescingTest override > cacheConfiguration method from IgniteCacheStoreSessionWriteBehindAbstractTest > to switch TestStore into TestNonCoalescingStore. > But IgniteCacheStoreSessionWriteBehindAbstractTest.getConfiguration > cacheStoreFactory explicitly set to TestStore for ccfg1. > Need to remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5390) But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest
[ https://issues.apache.org/jira/browse/IGNITE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev updated IGNITE-5390: -- Environment: (was: 1.9.3) > But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest > - > > Key: IGNITE-5390 > URL: https://issues.apache.org/jira/browse/IGNITE-5390 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Trivial > > IgniteCacheTxStoreSessionWriteBehindCoalescingTest override > cacheConfiguration method from IgniteCacheStoreSessionWriteBehindAbstractTest > to switch TestStore into TestNonCoalescingStore. > But IgniteCacheStoreSessionWriteBehindAbstractTest.getConfiguration > cacheStoreFactory explicitly set to TestStore for ccfg1. > Need to remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5390) But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest
Alexander Belyak created IGNITE-5390: Summary: But in IgniteCacheTxStoreSessionWriteBehindCoalescingTest Key: IGNITE-5390 URL: https://issues.apache.org/jira/browse/IGNITE-5390 Project: Ignite Issue Type: Bug Environment: 1.9.3 Reporter: Alexander Belyak Assignee: Alexander Belyak Priority: Trivial IgniteCacheTxStoreSessionWriteBehindCoalescingTest override cacheConfiguration method from IgniteCacheStoreSessionWriteBehindAbstractTest to switch TestStore into TestNonCoalescingStore. But IgniteCacheStoreSessionWriteBehindAbstractTest.getConfiguration cacheStoreFactory explicitly set to TestStore for ccfg1. Need to remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5386) Inactive mode must be forced on starting up grid with persistence is enabled
[ https://issues.apache.org/jira/browse/IGNITE-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin reassigned IGNITE-5386: -- Assignee: Dmitriy Govorukhin (was: Sergey Chugunov) > Inactive mode must be forced on starting up grid with persistence is enabled > > > Key: IGNITE-5386 > URL: https://issues.apache.org/jira/browse/IGNITE-5386 > Project: Ignite > Issue Type: Task > Components: persistence >Reporter: Sergey Chugunov >Assignee: Dmitriy Govorukhin > Labels: important > Fix For: 2.1 > > > h2. Notes > There is an issue in grid startup documented in IGNITE-5363. > In a nutshell it is caused by double initialization of database memory and > disk structures when grid started in inactive mode gets activated. > To prevent this grid with persistence enabled must be started in the > following order > # Inactive mode must be forced if persistence is enabled (if node is starting > up in active mode and persistence is enabled, an exception must be thrown). > # During starting the node database is left uninitialized. > # When user triggers activating the cluster, database memory and disk > structures are initialized on all nodes. > h2. Acceptance Criteria > # Inactive mode is forced on grid startup when persistence is enabled. > # New node join scenario is properly covered. > # All persistence-related tests are passing, no new test failures are added. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
