Re: Stable binary key representation

Denis, Can you suggest a use-case where identity resolver is needed (given that we agree that a key must contain only valuable fields)? 2017-04-05 22:08 GMT+03:00 Denis Magda : > Where do you want to remove the identity resolvers from? If it’s related > to the internals of Hibernate module then

[GitHub] ignite pull request #1733: IGNITE-4885 .NET: Disallow abstract and open gene...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1733 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[GitHub] ignite pull request #1738: IGNITE-4899 .NET: Review Dictionary usage in APIs

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1738 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

Re: Apache Ignite 2.0 Release

Yes, I think they have to be released as well. Igniters, who can take over these tasks and make them done by the code freeze? — Denis > On Apr 5, 2017, at 9:39 PM, Dmitriy Setrakyan wrote: > > *Denis*, we still have 5 issues that are *unassigned*. Are they supposed to > be getting into release

Re: Apache Ignite 2.0 Release

> *Denis Magda:* > IGNITE-1192 - Provide > integration with Spring Data Will be finished and merged by the code freeze date. I’m on a business trip now and don’t have extra time to complete the feature. Plus, following your template these are a

Re: jdbc vs jdbc2 packages

Ticket: https://issues.apache.org/jira/browse/IGNITE-4922 — Denis > On Mar 30, 2017, at 7:06 PM, Denis Magda wrote: > > Folks, > > I had a chance to validate usability of both Ignite JDBC drivers at PGConf > USA today trying to connect to t

Re: Apache Ignite 2.0 Release

Guys, Please provide a status underneath every ticket listed below, so we can get a full picture in one email thread: *Alexey Goncharuk:* IGNITE-3477 - Rework offheap storage IGNITE-4337 - Intr

[jira] [Created] (IGNITE-4922) JDBC Driver: renew thin client based solution

Denis Magda created IGNITE-4922: --- Summary: JDBC Driver: renew thin client based solution Key: IGNITE-4922 URL: https://issues.apache.org/jira/browse/IGNITE-4922 Project: Ignite Issue Type: Task

Re: Apache Ignite 2.0 Release

Dmitriy, You can find all the required tickets with contributors assigned here: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0#ApacheIgnite2.0-Requiredtickets In short, A

Re: Apache Ignite 2.0 Release

Denis, I think it will be worth while to list all the tickets by status together with a name of the engineer assigned to it. This way most folks involved would provide a response sooner. What do you think? D. On Wed, Apr 5, 2017 at 1:27 PM, Denis Magda wrote: > Igniters, > > What’s the overal

Re: Adding ML to Ignite, IGNITE-4572

Sorry for the late reply. Sure, you're always welcomed to join our community and participate in the development of modules of interest. As for ML, please keep an eye on this discussion where will break down ML activities a bit later. Denis On Wednesday, April 5, 2017, anantbietec wrote: > I am

Re: Adding ML to Ignite, IGNITE-4572

I am very enthusiatic about this project but sir i have not submitted PROPOSAL FOR THIS IN gsoc 2017 can i still be allowed to do this project As the reply comes very late i didnt know what are the tasks to do in this project . So i didnt prepare the proposal . Can we still have the discussion

Bug fix to IGNITE-4817

Hi guys, I've finished implementing bug fix to IGNITE-4817 .NET: Contains fails in LINQ when subquery comes from a variable Also I've queued 'Ignite Platform .NET' & 'Ignite Platform .NET Inspection' jobs on Team City: http://ci.ignite.apache.org

Re: Apache Ignite 2.0 Release

Igniters, What’s the overall status of 2.0 release? I see that many tickets related to the page memory [1] are still in the open state and, looks like, this new memory architecture has not been fully merged yet. In addition, a new version of H2 has to be released prior to 2.0. All this threat

[GitHub] ignite pull request #1745: IGNITE-4817

GitHub user gurustron opened a pull request: https://github.com/apache/ignite/pull/1745 IGNITE-4817 QueryParser switched to use CompoundExpressionTreeProcessor. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gurustron/ignite IGNI

Re: IGNITE-4188, savepoints with atomic cache?

IGNITE-2313 done, can you review it? PR: https://github.com/apache/ignite/pull/1709/files JIRA: https://issues.apache.org/jira/browse/IGNITE-2313 CI: http://ci.ignite.apache.org/viewType.html?buildTypeId= IgniteTests_RatJavadoc&branch_IgniteTests=pull%2F1709% 2Fhead&tab=buildTypeStatusDiv 2017-03

Re: IGNITE-2313 - ready for review

Em... sorry, always forgot about meaningful title( Discussion? Yeah, I'll do it. 2017-04-05 22:15 GMT+03:00 Denis Magda : > Dmitriy R., may I ask you to make a title and description of review > request more meaningful? Looking at email's subject and body neither me nor > anyone else have an idea

Re: IGNITE-2313 - ready for review

Dmitriy R., may I ask you to make a title and description of review request more meaningful? Looking at email's subject and body neither me nor anyone else have an idea what you ask to review. As a result most of community members will simply ignore your review request skipping the message. Don’

Re: Stable binary key representation

Where do you want to remove the identity resolvers from? If it’s related to the internals of Hibernate module then it’s fine but if you suggest removing identity resolvers public interfaces then it might be a haste decision. — Denis > On Apr 5, 2017, at 7:42 AM, Alexey Goncharuk > wrote: > >

Re: Adding ML to Ignite, IGNITE-4572

These are some suggestions from Nikita that were sent to Alper privately that might be useful for other candidates: Alper, Here are some of the immediate tasks we'll be working on past 2.0 release (and you are 100% welcome to tackle them if you find them interesting): (1) Linear regression algo

Re: IGNITE - 4760 : working in hibernate module

> How to reproduce situation when updates can be recorded to another region? Don’t you just need to define multiple caches that will be mapped to Hibernate regions and initiate a transaction that updates several regions (caches) at once? — Denis > On Apr 3, 2017, at 10:39 AM, Вадим Опольский

Presenting Apache Ignite in Miami, May 2017

Igniters, I’m presenting two talks related to Apache Ignite in May at ASF Apache Con and Apache BigData conferences. Latest news: https://ignite.apache.org/news.html Direct links: https://apachecon2017.sched.com/event/9zot?iframe=no

[GitHub] ignite pull request #1744: Ignite 3477 master client offheap fix

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1744 Ignite 3477 master client offheap fix DO NOT MERGE. PR only to run tests on TC. You can merge this pull request into a Git repository by running: $ git pull https://githu

[GitHub] ignite pull request #1743: ignite-4797: Added API for system allocated size ...

GitHub user kartiksomani opened a pull request: https://github.com/apache/ignite/pull/1743 ignite-4797: Added API for system allocated size in CacheMetrics Addressed comments made by Andrey Gura https://issues.apache.org/jira/browse/IGNITE-4797 You can merge this pull requ

[jira] [Created] (IGNITE-4921) Refactor segments array in PageMemoryNoStoreImpl

Ivan Rakov created IGNITE-4921: -- Summary: Refactor segments array in PageMemoryNoStoreImpl Key: IGNITE-4921 URL: https://issues.apache.org/jira/browse/IGNITE-4921 Project: Ignite Issue Type: Imp

[jira] [Created] (IGNITE-4920) LocalDeploymentSpi resources cleanup on spi.register() might clean resources from other tasks using delegating classloader.

Alexei Scherbakov created IGNITE-4920: - Summary: LocalDeploymentSpi resources cleanup on spi.register() might clean resources from other tasks using delegating classloader. Key: IGNITE-4920 URL: https://issues

[GitHub] ignite pull request #1742: Ignite-4919 Remove support BinaryIdentityResolver

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/1742 Ignite-4919 Remove support BinaryIdentityResolver You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4919

[GitHub] ignite pull request #1468: IGNITE-4511: Set QueryIndexType.SORTED by default...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1468 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1257: IGNITE-4259: Geospatial functionality is broken i...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1257 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1082: IGNITE-3925: Output process ID to the log during ...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1082 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-4919) Remove support BinaryIdentityResolver

Dmitriy Govorukhin created IGNITE-4919: -- Summary: Remove support BinaryIdentityResolver Key: IGNITE-4919 URL: https://issues.apache.org/jira/browse/IGNITE-4919 Project: Ignite Issue Type

Re: ScanQuery With BinaryObject

I've creted a ticket [1]. [1] https://issues.apache.org/jira/browse/IGNITE-4918 On Wed, Apr 5, 2017 at 4:42 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Looks like a bug. Can you create a ticket? > > -Val > > On Wed, Apr 5, 2017 at 2:01 AM, Andrey Mashenkov < > andrey.mashen

[GitHub] ignite pull request #1741: IGNITE-4914 distributing marshaller mappings for ...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1741 IGNITE-4914 distributing marshaller mappings for multiple platforms fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[jira] [Created] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.

Andrew Mashenkov created IGNITE-4918: Summary: ScanQuery filter class code is not updated on server once it has been changed on client. Key: IGNITE-4918 URL: https://issues.apache.org/jira/browse/IGNITE-4918

Re: Async listeners for IgniteFuture

Hi, Dmitry. Is make sense use custom named executors [1] in your API? i.e. adds method passed executor name? [1] https://issues.apache.org/jira/browse/IGNITE-4699 On 05.04.2017 12:15, Dmitry Karachentsev wrote: Hello everyone! I'm working on this ticket [1] and Vladimir made a review where h

Re: ScanQuery With BinaryObject

Looks like a bug. Can you create a ticket? -Val On Wed, Apr 5, 2017 at 2:01 AM, Andrey Mashenkov wrote: > To reproduce > - start standalone server > - run test, it should work fine. > - run test with changed filter code, it will return same results. > > > On Wed, Apr 5, 2017 at 11:40 AM, Valent

Re: issue with Hibernate 2L cache region factory ignite-1.8

Hello everybody! Cameron write please. How did you recreated mistake that the wrong regions/caches were being updated? I tried to do it in HibernateL2CacheConfigurationSelfTest.java - testEntityCacheNonStrictFails. After: e2forUpdate.setName("XXX"); session.update(e2forUpdate); Both reg

[GitHub] ignite pull request #1740: Ignite 1.8.6

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1740 Ignite 1.8.6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.8.6 Alternatively you can review and apply the

[GitHub] ignite pull request #1739: Ignite-1267-1

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1739 Ignite-1267-1 for test purpose only You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1267-1 Alternatively you c

Re: Question: local cache on client nodes

In that case I suggest the following solution based on the same model of allocating memory on node startup. So, on client nodes if user provides configuration for MemoryPolicies, we allocate all memory on node startup. But if no MemoryPolicy configuration is provided on client node startup, no def

[GitHub] ignite pull request #1738: IGNITE-4899 .NET: Review Dictionary usage in APIs

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1738 IGNITE-4899 .NET: Review Dictionary usage in APIs You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-4899 Alternatively

[GitHub] ignite pull request #1737: IGNITE-4535

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/1737 IGNITE-4535 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4535-master Alternatively you can review and apply

[GitHub] ignite pull request #1620: Ignite 4535

Github user ilantukh closed the pull request at: https://github.com/apache/ignite/pull/1620 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is e

Re: Non-collocated distributed SQL Joins across caches over separate cluster groups

I suggest we continue the conversation on the user list. My bad for pinging the email to both channels. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Non-collocated-distributed-SQL-Joins-across-caches-over-separate-cluster-groups-tp16136p16163.html Sent

Re: one point optimisation

would like to add 1 phase optimisation isn't gonna work if write through is enabled. ср, 5 апр. 2017 г. в 15:23, Антон Чураев : > Maybe it will be useful to update the documentation? > > 2017-04-05 15:15 GMT+03:00 ALEKSEY KUZNETSOV : > > > Thank you for help! > > > > ср, 5 апр. 2017 г. в 15:14, A

Fwd: IGNITE - 4760 : added test

Hello everybody! Added test. Test fails after session.update(e2forUpdate). This update must put into ENTITY2_NAME region, but it puts into ENTITY1_NAME and ENTITY2_NAME regions. https://github.com/vadopolski/ignite/pull/1 Is it true? I have no idea how to change the method threadLocalForCache t

Re: Non-collocated distributed SQL Joins across caches over separate cluster groups

Sergi, Does it means that "broken" FairAffinityFunction can lead to wrong SQL query result? As we know, using FairAF have no guarantee that same parititions of different caches can belongs to different nodes in some cases. On Wed, Apr 5, 2017 at 1:47 PM, Sergi Vladykin wrote: > Hi, > > Moreover

Re: one point optimisation

Maybe it will be useful to update the documentation? 2017-04-05 15:15 GMT+03:00 ALEKSEY KUZNETSOV : > Thank you for help! > > ср, 5 апр. 2017 г. в 15:14, Alexey Goncharuk : > > > This optimization does not work when near cache is enabled because we > need > > the same ordering on near nodes. You

Re: one point optimisation

Thank you for help! ср, 5 апр. 2017 г. в 15:14, Alexey Goncharuk : > This optimization does not work when near cache is enabled because we need > the same ordering on near nodes. You should see the expected number of > messages with near cache disabled. > > 2017-04-05 15:09 GMT+03:00 ALEKSEY KUZN

Re: one point optimisation

This optimization does not work when near cache is enabled because we need the same ordering on near nodes. You should see the expected number of messages with near cache disabled. 2017-04-05 15:09 GMT+03:00 ALEKSEY KUZNETSOV : > yes > > ср, 5 апр. 2017 г. в 15:07, Alexey Goncharuk : > > > Do you

Re: one point optimisation

yes ср, 5 апр. 2017 г. в 15:07, Alexey Goncharuk : > Do you have a near cache enabled? > > 2017-04-05 15:00 GMT+03:00 ALEKSEY KUZNETSOV : > > > The test shows as follows: > > assertMessageCount(GridNearTxPrepareRequest.class, 1); > > assertMessageCount(GridDhtTxPrepareRequ

Re: one point optimisation

Do you have a near cache enabled? 2017-04-05 15:00 GMT+03:00 ALEKSEY KUZNETSOV : > The test shows as follows: > assertMessageCount(GridNearTxPrepareRequest.class, 1); > assertMessageCount(GridDhtTxPrepareRequest.class, 1); > assertMessageCount(GridDhtTxPrepareR

Re: one point optimisation

The test shows as follows: assertMessageCount(GridNearTxPrepareRequest.class, 1); assertMessageCount(GridDhtTxPrepareRequest.class, 1); assertMessageCount(GridDhtTxPrepareResponse.class, 1); assertMessageCount(GridNearTxPrepareResponse.class, 1);

Re: one point optimisation

Aleksey, Can you elaborate on which of the extra messages you observe? --AG 2017-04-04 14:17 GMT+03:00 ALEKSEY KUZNETSOV : > any thoughts on one phase commit realization ? > > пн, 3 апр. 2017 г. в 19:35, ALEKSEY KUZNETSOV : > > > I've attached test that prints messages exchange . Which shows us

[GitHub] ignite pull request #1736: IGNITE-4917: BinaryObjectBuilder field value acce...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1736 IGNITE-4917: BinaryObjectBuilder field value access failed if its serialized with optimal marshaller Fixed failure when accessing BinaryObjectBuilder field value serialized with OptimizedMarsha

[GitHub] ignite pull request #1735: Ignite-4917-1

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1735 Ignite-4917-1 for test purposes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4917-1 Alternatively you can r

Re: Stable binary key representation

+1, I see no other reasons to keep it. 2017-04-05 13:59 GMT+03:00 Sergi Vladykin : > +1 > > Lets drop them. > > Sergi > > 2017-04-05 13:50 GMT+03:00 Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> > : > > > Hi guys, i implemented proxy for IgniteCache in hibernate integration, > this > > pro

[GitHub] ignite pull request #1734: IGNITE-4915 Remove deprecated methods at the publ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1734 IGNITE-4915 Remove deprecated methods at the public API You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-

[jira] [Created] (IGNITE-4917) BinaryObjectBuilder field value access failed if its serialized with optimal marshaller

Andrew Mashenkov created IGNITE-4917: Summary: BinaryObjectBuilder field value access failed if its serialized with optimal marshaller Key: IGNITE-4917 URL: https://issues.apache.org/jira/browse/IGNITE-4917

Re: NearCache transaction qeustion

sorry, but what is sync/async policy ? пт, 31 мар. 2017 г. в 19:26, Dmitriy Setrakyan : > On Fri, Mar 31, 2017 at 6:29 AM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > > wrote: > > > Hi all! > > Consider we have 4 nodes. Node1 contains key1, Node2 contains key1 > backup, > > and Node3 near-co

[GitHub] ignite pull request #1733: IGNITE-4885 .NET: Disallow abstract and open gene...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1733 IGNITE-4885 .NET: Disallow abstract and open generic types in BinaryConfiguration You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/

Re: Stable binary key representation

+1 Lets drop them. Sergi 2017-04-05 13:50 GMT+03:00 Dmitriy Govorukhin : > Hi guys, i implemented proxy for IgniteCache in hibernate integration, this > proxy transformate cacheKey to our key wrapper, leaves only required > field. I think we can remove identity resolve, it should not broke > i

Re: IGNITE-4535 : Add option to store deserialized values on-heap

On Wed, Apr 5, 2017 at 2:52 AM, Ilya Lantukh wrote: > Dmitry, > > 1. Setting an eviction policy should not be a mechanism to enable the > > on-heap cache. We already have eviction policies off-heap as well, and > they > > don't enable anything. On top of that, the eviction policy should not be >

Re: Stable binary key representation

Hi guys, i implemented proxy for IgniteCache in hibernate integration, this proxy transformate cacheKey to our key wrapper, leaves only required field. I think we can remove identity resolve, it should not broke integration with hibernate. Any objections? On Wed, Mar 29, 2017 at 11:07 PM, Valentin

Re: IGNITE-4535 : Add option to store deserialized values on-heap

I think having pure on-heap cache is good idea. Sergi 2017-04-05 12:52 GMT+03:00 Ilya Lantukh : > Dmitry, > > 1. Setting an eviction policy should not be a mechanism to enable the > > on-heap cache. We already have eviction policies off-heap as well, and > they > > don't enable anything. On top

Re: Non-collocated distributed SQL Joins across caches over separate cluster groups

Hi, Moreover distributed joins can be executed only between caches with the same affinity (same partitions on the same nodes). Keep in mind that distributed join is already a "last resort" thing and you have to prefer collocated joins as much as possible, if you want to achieve good performance.

[jira] [Created] (IGNITE-4916) Hibernate support improvement

Andrew Mashenkov created IGNITE-4916: Summary: Hibernate support improvement Key: IGNITE-4916 URL: https://issues.apache.org/jira/browse/IGNITE-4916 Project: Ignite Issue Type: Task

Re: IGNITE-4535 : Add option to store deserialized values on-heap

Dmitry, 1. Setting an eviction policy should not be a mechanism to enable the > on-heap cache. We already have eviction policies off-heap as well, and they > don't enable anything. On top of that, the eviction policy should not be a > requirement for the on-heap cache. User should still be able to

[jira] [Created] (IGNITE-4915) Remove deprecated methods at the public API

Taras Ledkov created IGNITE-4915: Summary: Remove deprecated methods at the public API Key: IGNITE-4915 URL: https://issues.apache.org/jira/browse/IGNITE-4915 Project: Ignite Issue Type: Sub-

Async listeners for IgniteFuture

Hello everyone! I'm working on this ticket [1] and Vladimir made a review where he has concerns about implementation. I want to know community opinion about second one: where user callbacks should be processed by default? For that purpose I used public pool for now, but this could lead to de

Non-collocated distributed SQL Joins across caches over separate cluster groups

Igniters, Is it correct to assume the following: We have an Ignite cluster comprised of 2 cluster groups A & B that have different caches deployed. We use an Ignite client to obtain API access to the whole cluster and execute a join query that joins data across the 2 caches My understanding is

Re: ScanQuery With BinaryObject

To reproduce - start standalone server - run test, it should work fine. - run test with changed filter code, it will return same results. On Wed, Apr 5, 2017 at 11:40 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Can you provide the test? > > -Val > > On Wed, Apr 5, 2017 at 1

[GitHub] ignite pull request #1667: IGNITE-4839 Remove CacheTypeMetadata

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1667 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[jira] [Created] (IGNITE-4914) Dynamic type registration hangs for platformId > 0 on node restart

Pavel Tupitsyn created IGNITE-4914: -- Summary: Dynamic type registration hangs for platformId > 0 on node restart Key: IGNITE-4914 URL: https://issues.apache.org/jira/browse/IGNITE-4914 Project: Ignit

Re: ScanQuery With BinaryObject

Can you provide the test? -Val On Wed, Apr 5, 2017 at 1:37 AM, Andrey Mashenkov wrote: > Hi Val, > > I run test with no filter class in server classpath. I've got an error > wiith peerClassLoading disabled, which is ok as server can't unmarshal > filter object. > But with peerClassLoading enabl

Re: ScanQuery With BinaryObject

Hi Val, I run test with no filter class in server classpath. I've got an error wiith peerClassLoading disabled, which is ok as server can't unmarshal filter object. But with peerClassLoading enabled, query works fine but looks like filter class won't be updated on server. On Wed, Apr 5, 2017 at 1

Re: ScanQuery With BinaryObject

Andrey, Marshaller cache does not store classes, only class names. So I'm not sure what you mean by this. I looked at the code and it seems I was wrong - peer class loading does work for scan query filter, which is good. But as I mentioned before, if the class is available on local classpath, it

IGNITE-2313 - ready for review

Hello, please review. PR: https://github.com/apache/ignite/pull/1709/files JIRA: https://issues.apache.org/jira/browse/IGNITE-2313 CI: http://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests_RatJavadoc&branch_IgniteTests=pull%2F1709%2Fhead&tab=buildTypeStatusDiv

[jira] [Created] (IGNITE-4913) Update yardstick properties files

Ilya Suntsov created IGNITE-4913: Summary: Update yardstick properties files Key: IGNITE-4913 URL: https://issues.apache.org/jira/browse/IGNITE-4913 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #1732: IGNITE-4856 .NET: StopAll on AppDomain unload

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1732 IGNITE-4856 .NET: StopAll on AppDomain unload You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4856 Alternative

[jira] [Created] (IGNITE-4912) Fix testDeployCalledAfterCacheStart and testDeployCalledBeforeCacheStart tests

Dmitry Karachentsev created IGNITE-4912: --- Summary: Fix testDeployCalledAfterCacheStart and testDeployCalledBeforeCacheStart tests Key: IGNITE-4912 URL: https://issues.apache.org/jira/browse/IGNITE-4912

[jira] [Created] (IGNITE-4911) Fix tests #1

Dmitry Karachentsev created IGNITE-4911: --- Summary: Fix tests #1 Key: IGNITE-4911 URL: https://issues.apache.org/jira/browse/IGNITE-4911 Project: Ignite Issue Type: Bug Compone

Re: ScanQuery With BinaryObject

Hi Val, Filter object serialized and send inside GridCacheQueryRequest, and then it is deserialized on server side and loaded by cache class loader. Looks like filter class is cached in marshaller cache. On Tue, Apr 4, 2017 at 4:43 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: