Re: Where and how to store metrics for queries.

[Alexey Kuznetsov]

Dima & Val,

My first intention was to store metrics locally and collect them on demand.

But after that I start to think about following scenarios:

What if we have a grid with clients that connected to grid, execute some
query and *disconnected*?
In this case we would have no option to collect metrics about what queries
were executed on grid.

Also, very often clients may resided in a *slow* network segment and
sending a task for collecting metrics
 from *fast server nodes* and *slow clients* may take a lot of time in case
of large grid.

Could you suggest me how I could deal with two mentioned above cases?

Or we could ignore them for now?

-- 
Alexey Kuznetsov

Re: Official Apache Ignite meetup - Sept. 22nd - London

[Alexey Kuznetsov]

Hi Christos,

I'like this video.
Looking forward for new videos!

Denis, does it make sense to add link to this video to
https://ignite.apache.org "Latest news" section?

-- 
Alexey Kuznetsov

Re: Official Apache Ignite meetup - Sept. 22nd - London

[Denis Magda]

Hi Christos,

Thanks for sharing! The use case is really unique. It was useful to learn how 
Apache Ignite and GridGain are applicable in betting and gambling platforms.

—
Denis

> On Oct 6, 2016, at 3:27 AM, Christos Erotocritou  
> wrote:
> 
> Hello Igniters,
> 
> The recording from our most recent Ignite London meetup is ready to share.
> 
> This time we had the pleasure of having Sam Lawrence from FSB Technologies 
> talk about how they have used Apache Ignite to transform their online sports 
> betting platform.
> 
> Check it out: https://www.youtube.com/watch?v=rJZf1wIU1TE 
> 
> 
> Please share your feedback regarding the content, recordings and style to 
> help us shape these sessions as we move forward. Also, don’t forget to 
> subscribe to our Apache Ignite YouTube channel to keep up to date with any 
> new content we post.
> 
> Cheers!
> 
> Christos
> 
>> On 16 Sep 2016, at 09:28, Christos Erotocritou > > wrote:
>> 
>> We will try to stream the event live. But we will certainly share the video 
>> and slides following the meetup. 
>> 
>> On Friday, 16 September 2016, Alexey Kuznetsov > > wrote:
>> It is possible to see slides or even meetup video?
>> 
>> 16 Сен 2016 г. 14:09 пользователь "Christos Erotocritou" <
>> chris...@gridgain.com > написал:
>> 
>> > Hello Igniters!
>> >
>> > Following our first and successful official Ignite meetup
>> > > > > in London, we are now
>> > excited to announce our next gathering.
>> >
>> > Our second session > > > will be on the 22nd
>> > of September and we've invited FSB Technologies > > > to
>> > share their Ignite story.
>> >
>> > Event Link: http://meetu.ps/e/BVTs1/1RGQ6/f 
>> > 
>> >
>> > If you are in London and have time please join us for a great afternoon of
>> > interesting talks, beers & pizzas!
>> >
>> > Please help us spread the word and grow our community by sharing this
>> > invite far and wide.
>> >
>> > Thanks,
>> >
>> > Christos
>> >
>> >
> 

Re: Where and how to store metrics for queries.

[Valentin Kulichenko]

Alexey,

Why do you need to store metrics in cache? For all our metrics we just
store them locally and aggregate on demand. What is the reason for
different approach here?

Generally, I think we should avoid using system caches wherever possible,
and probably rework current usages of such caches. If global notification
is needed, custom discovery message is much better option.

-Val

On Wed, Oct 5, 2016 at 9:56 PM, Alexey Kuznetsov 
wrote:

> Hi, All!
>
> I'm working on IGNITE-3443 "Implement collecting what SQL statements
> executed on cluster and their metrics." [1]
>
> And I need to discuss where and how store collected metrics.
>
> I see 2 options:
>
> 1) Store metrics in a special separate replicated cache. In this case I
> could easily add, collect and evict metrics. But I will need  somehow made
> this cache "system" in order to not show it for users (for example in Visor
> console).
>
> 2) Store metrics in system utility cache. In this case I could easily add
> metrics, but collecting and evicting will be not so trivial...
>
> Which way should I choose?
>
> Please, share your thoughts.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-3443
>
> --
> Alexey Kuznetsov
>

Re: Where and how to store metrics for queries.

[Dmitriy Setrakyan]

Alexey, why do you need to store the SQL metrics in a cache? I would avoid
it. Instead, is there a way to have a local metric store on every node and
have WebConsole send a task to each node and aggregate the results?

D.

On Wed, Oct 5, 2016 at 9:56 PM, Alexey Kuznetsov 
wrote:

> Hi, All!
>
> I'm working on IGNITE-3443 "Implement collecting what SQL statements
> executed on cluster and their metrics." [1]
>
> And I need to discuss where and how store collected metrics.
>
> I see 2 options:
>
> 1) Store metrics in a special separate replicated cache. In this case I
> could easily add, collect and evict metrics. But I will need  somehow made
> this cache "system" in order to not show it for users (for example in Visor
> console).
>
> 2) Store metrics in system utility cache. In this case I could easily add
> metrics, but collecting and evicting will be not so trivial...
>
> Which way should I choose?
>
> Please, share your thoughts.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-3443
>
> --
> Alexey Kuznetsov
>

[jira] [Created] (IGNITE-4045) .Net: Support DML API

[Denis Magda (JIRA)]

Denis Magda created IGNITE-4045:
---

 Summary: .Net: Support DML API
 Key: IGNITE-4045
 URL: https://issues.apache.org/jira/browse/IGNITE-4045
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Reporter: Denis Magda
Assignee: Pavel Tupitsyn
 Fix For: 1.9


Ignite's Java component will provide support for DML soon (IGNITE-2294). At she 
same time DML will be supported at the level of ODBC and JDBC drivers.

As the next step we should include the similar functionality into Ignite.NET by 
doing the following:
- Implement DML API;
- Enhance {{QueryExample.cs}} by doing INSERTs instead of cache.puts and adding 
UPDATE and DELETE operation examples.
- Add documentation to Ignite.NET readme.io covering the feature. Most like 
most of the content can be take from the general documentation when this ticket 
IGNITE-4018 is ready.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: IGNITE-3722 Cached in a file text must be written with UTF-8 charset, not default

[Saikat Maitra]

Thank you Semen !!!

Regards
Saikat

On Thu, Oct 6, 2016 at 11:13 AM, Semyon Boikov  wrote:

> Hi,
>
> I reviewed and merged your fix. Thanks for contribution!
>
> Thanks!
>
> On Tue, Oct 4, 2016 at 10:06 PM, Saikat Maitra 
> wrote:
>
> > Hi,
> >
> > I have raised PR[1] for the following jira ticket[2].
> >
> > Please review and let me know if any changes required.
> >
> > Regards,
> >
> > Saikat
> >
> > [1] https://github.com/apache/ignite/pull/1144
> >
> > [2] https://issues.apache.org/jira/browse/IGNITE-3722
> >
>

[GitHub] ignite pull request #1151: Ignite 4011

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

https://github.com/apache/ignite/pull/1151

Ignite 4011



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4011

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1151.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 #1151


commit 86913ccb547f20ab38b1418d9be32907123e3610
Author: Alexander Paschenko 
Date:   2016-10-04T21:36:59Z

IGNITE-4011 Automatic hash code computing for BinaryBuilder constructed 
objects

commit fe9991f0cf1e960db7f5e5d1803af04f50850e51
Author: Alexander Paschenko 
Date:   2016-10-06T14:03:58Z

Merge branch 'master' into ignite-4011




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-4044) Add an option to always authenticate local node

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-4044:
--

 Summary: Add an option to always authenticate local node
 Key: IGNITE-4044
 URL: https://issues.apache.org/jira/browse/IGNITE-4044
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Dmitriy Govorukhin
Assignee: Dmitriy Govorukhin


Currently authenticator is called during the startup only if the new node is 
the first one in the topology. This in counterintuitive and introduces 
unpredictable behavior when global authentication is enabled - the node may or 
may not call the authenticator depending on the starting order.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4043) Visor CMD: cache scan - support execution on selected node only

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-4043:


 Summary: Visor CMD: cache scan - support execution on selected 
node only
 Key: IGNITE-4043
 URL: https://issues.apache.org/jira/browse/IGNITE-4043
 Project: Ignite
  Issue Type: Task
  Components: wizards
Affects Versions: 1.7
Reporter: Alexey Kuznetsov


See: 
http://stackoverflow.com/questions/39887651/get-cache-entrieskeys-values-list-on-particular-node-in-apache-ignite#



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Official Apache Ignite meetup - Sept. 22nd - London

[Christos Erotocritou]

Hello Igniters,

The recording from our most recent Ignite London meetup is ready to share.

This time we had the pleasure of having Sam Lawrence from FSB Technologies talk 
about how they have used Apache Ignite to transform their online sports betting 
platform.

Check it out: https://www.youtube.com/watch?v=rJZf1wIU1TE 


Please share your feedback regarding the content, recordings and style to help 
us shape these sessions as we move forward. Also, don’t forget to subscribe to 
our Apache Ignite YouTube channel to keep up to date with any new content we 
post.

Cheers!

Christos

> On 16 Sep 2016, at 09:28, Christos Erotocritou  wrote:
> 
> We will try to stream the event live. But we will certainly share the video 
> and slides following the meetup. 
> 
> On Friday, 16 September 2016, Alexey Kuznetsov  > wrote:
> It is possible to see slides or even meetup video?
> 
> 16 Сен 2016 г. 14:09 пользователь "Christos Erotocritou" <
> chris...@gridgain.com > написал:
> 
> > Hello Igniters!
> >
> > Following our first and successful official Ignite meetup
> >  > > in London, we are now
> > excited to announce our next gathering.
> >
> > Our second session  > > will be on the 22nd
> > of September and we've invited FSB Technologies  > > to
> > share their Ignite story.
> >
> > Event Link: http://meetu.ps/e/BVTs1/1RGQ6/f 
> > 
> >
> > If you are in London and have time please join us for a great afternoon of
> > interesting talks, beers & pizzas!
> >
> > Please help us spread the word and grow our community by sharing this
> > invite far and wide.
> >
> > Thanks,
> >
> > Christos
> >
> >

[jira] [Created] (IGNITE-4042) Refactor async operations

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4042:
--

 Summary: Refactor async operations
 Key: IGNITE-4042
 URL: https://issues.apache.org/jira/browse/IGNITE-4042
 Project: Ignite
  Issue Type: Sub-task
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.8


Currently async operations are executed in two steps:
- start an operation (Cache.Get)
- get the future (UU.TargetListenFuture* methods)

This separation is unnecessary. See if we can perform asyn operations in one 
JNI call.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Concurrent read-through

[Yakov Zhdanov]

I don't think there is a way to fix this other than having some bounded
collection of futures finished with "null" result.

--Yakov

2016-10-04 23:09 GMT+03:00 Dmitriy Setrakyan :

> Hm... sounds like a bug.
>
> On Tue, Oct 4, 2016 at 1:06 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Folks,
> >
> > I noticed strange behavior when read-through done from several concurrent
> > threads. Basically, if miss happened in two thread, they can both load
> the
> > value from store. We have CacheStoreBalancingWrapper which I believe is
> > supposed to solve this, but there is still a race, because the loading
> can
> > start after the future in the wrapper is already completed and removed. I
> > think it can potentially be a performance issue in case the loading
> process
> > takes significant amount of time.
> >
> > Is this by design and is there any way to make it more reliable? Why
> don't
> > we load within the entry sync block, like we do with updates?
> >
> > -Val
> >
>

[GitHub] ignite pull request #1150: Ignite 4041

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/1150

Ignite 4041



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4041

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1150.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 #1150


commit a4c63ae113931615e940ada2411ebce32dba5db8
Author: iveselovskiy 
Date:   2016-09-30T07:45:13Z

IGNITE-3998: IGFS: Enabled 
IgfsAbstractSelfTest.testCreateConsistencyMultithreaded. This closes #1129.

commit a12298c0baf19407f3110ba3c4f0aab88b67946d
Author: Igor Sapego 
Date:   2016-09-30T08:00:51Z

IGNITE-3868: ODBC: Fixed connection string parsing. This closes #1051.

commit 5e7ef8644ad824b87d4797e59133eb783ff8b098
Author: vozerov-gridgain 
Date:   2016-10-03T07:37:25Z

Merge branch 'ignite-1.6.9' into ignite-1.6.10

commit 59b46d3e6ea073d054ca2262d676b055a74bbb1f
Author: vozerov-gridgain 
Date:   2016-10-03T07:40:04Z

IGNITE-2881: Fixed SPI queries.

commit 0b66d2d7b695cf370a4b8a717844ad67742c6090
Author: sboikov 
Date:   2016-10-03T09:04:03Z

ignite-3601 Do not check version on commit for read-only serializable 
transactions.

commit 9f211e413332931f0fb1190744ddd7c7f38fd213
Author: tledkov-gridgain 
Date:   2016-10-03T09:26:12Z

IGNITE-3645: IGFS: Local secondary: Implemented update() operation. This 
closes #1003.

commit fa698d6fcfde0006423ef009337dbef58ac62515
Author: vozerov-gridgain 
Date:   2016-10-03T10:33:12Z

Fixed TcpDiscoverySnapshotHistoryTest intermittent failures caused by 
multicast IP finder.

commit bba019fd5076412ca43c10a32fd300b6031ccd0b
Author: vozerov-gridgain 
Date:   2016-10-03T14:25:20Z

IGNITE-3980: Processed failing tests in query suites. This closes #1137.

commit a92f20b5cc75e6b80b2731da0192723526b0c1dc
Author: vozerov-gridgain 
Date:   2016-10-04T11:10:26Z

IGNITE-3597: Removed static work directory.

commit 23461b8d33922772ef8e7217e9e87b3f3b0b37b1
Author: vozerov-gridgain 
Date:   2016-10-06T07:14:59Z

IGNITE-4001: Timeouts for threads in Ignite pools. This closes #1130.

commit b94b0aeae4c42b1d35128c6b1de97e3fa318d497
Author: tledkov-gridgain 
Date:   2016-10-06T07:22:50Z

IGNITE-3163 IGFS: Added working directory support to 
IgniteHadoopIgfsSecondaryFileSystem. This closes #1030. This closes #1058. This 
closes #1132.

commit 16bf13280e04bc0b88ca046dee6ba10e0190d2f3
Author: vozerov-gridgain 
Date:   2016-10-06T08:28:11Z

IGNITE-4041: Created processor and refactored IO manager.

commit df1e3d0f1900f0f05c9793364420b55423996583
Author: vozerov-gridgain 
Date:   2016-10-06T08:39:02Z

Finalized.

commit 1f2db84dd9408e84f9099dcbce6e1f9eac7379b4
Author: vozerov-gridgain 
Date:   2016-10-06T08:40:24Z

Minors.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-4041) Consistent thread pool resolution for IO and closures.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4041:
---

 Summary: Consistent thread pool resolution for IO and closures.
 Key: IGNITE-4041
 URL: https://issues.apache.org/jira/browse/IGNITE-4041
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.7
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Minor
 Fix For: 1.8






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4040) Web console: Do not scroll summary panel, scroll only table content

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-4040:
--

 Summary: Web console: Do not scroll summary panel, scroll only 
table content
 Key: IGNITE-4040
 URL: https://issues.apache.org/jira/browse/IGNITE-4040
 Project: Ignite
  Issue Type: Improvement
Reporter: Pavel Konstantinov
Priority: Trivial


Currently we scroll whole panel - header + table, but in this case header is 
not visible. More convenient to scroll a table content only.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Start threads in our pools on demand?

[Vladimir Ozerov]

Implemented. Will appear in master soon. Benchmarks shown no performance
drop.

On Thu, Sep 29, 2016 at 3:16 PM, Vladimir Ozerov 
wrote:

> Ignite node thread dump after applying quick and dirty solution - just
> added *ThreadPoolExecutor.allowCoreThreadTimeOut(true)* to base thread
> pool:
>
> "srvc-deploy-#20%null%"
> "exchange-worker-#19%null%"
> "ttl-cleanup-worker-#18%null%"
> "grid-time-coordinator-#17%null%"
> "grid-time-server-reader-#16%null%"
> "disco-event-worker-#15%null%"
> "tcp-disco-ip-finder-cleaner-#5%null%"
> "tcp-disco-srvr-#4%null%"
> "tcp-disco-msg-worker-#3%null%"
> "grid-data-loader-flusher-#14%null%"
> "tcp-comm-worker-#1%null%"
> "grid-nio-worker-3-#12%null%"
> "grid-nio-worker-2-#11%null%"
> "grid-nio-worker-1-#10%null%"
> "grid-nio-worker-0-#9%null%"
> "nio-acceptor-#8%null%"
> "grid-timeout-worker-#7%null%"
>
> Looks pretty nice to me. Now need to finalize and benchmark it.
>
> On Thu, Sep 29, 2016 at 2:05 PM, Vladimir Ozerov 
> wrote:
>
>> Created ticket: https://issues.apache.org/jira/browse/IGNITE-4001
>>
>> On Thu, Sep 29, 2016 at 12:25 PM, Alexey Kuznetsov <
>> akuznet...@gridgain.com> wrote:
>>
>>> Just as idea -
>>>
>>> if we implement stop thread after some idle time, may be it make sense to
>>> add a line to log about this?
>>>
>>> --
>>> Alexey Kuznetsov
>>>
>>
>>
>

[GitHub] ignite pull request #1130: Ignite 4001

[devozerov]

Github user devozerov closed the pull request at:

https://github.com/apache/ignite/pull/1130


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1149: IGNITE-4034 Get rid of specialized methods in pla...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/1149

IGNITE-4034 Get rid of specialized methods in platform targets



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-4034

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1149.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 #1149


commit a4c63ae113931615e940ada2411ebce32dba5db8
Author: iveselovskiy 
Date:   2016-09-30T07:45:13Z

IGNITE-3998: IGFS: Enabled 
IgfsAbstractSelfTest.testCreateConsistencyMultithreaded. This closes #1129.

commit a12298c0baf19407f3110ba3c4f0aab88b67946d
Author: Igor Sapego 
Date:   2016-09-30T08:00:51Z

IGNITE-3868: ODBC: Fixed connection string parsing. This closes #1051.

commit 5e7ef8644ad824b87d4797e59133eb783ff8b098
Author: vozerov-gridgain 
Date:   2016-10-03T07:37:25Z

Merge branch 'ignite-1.6.9' into ignite-1.6.10

commit 59b46d3e6ea073d054ca2262d676b055a74bbb1f
Author: vozerov-gridgain 
Date:   2016-10-03T07:40:04Z

IGNITE-2881: Fixed SPI queries.

commit 0b66d2d7b695cf370a4b8a717844ad67742c6090
Author: sboikov 
Date:   2016-10-03T09:04:03Z

ignite-3601 Do not check version on commit for read-only serializable 
transactions.

commit 9f211e413332931f0fb1190744ddd7c7f38fd213
Author: tledkov-gridgain 
Date:   2016-10-03T09:26:12Z

IGNITE-3645: IGFS: Local secondary: Implemented update() operation. This 
closes #1003.

commit fa698d6fcfde0006423ef009337dbef58ac62515
Author: vozerov-gridgain 
Date:   2016-10-03T10:33:12Z

Fixed TcpDiscoverySnapshotHistoryTest intermittent failures caused by 
multicast IP finder.

commit bba019fd5076412ca43c10a32fd300b6031ccd0b
Author: vozerov-gridgain 
Date:   2016-10-03T14:25:20Z

IGNITE-3980: Processed failing tests in query suites. This closes #1137.

commit a92f20b5cc75e6b80b2731da0192723526b0c1dc
Author: vozerov-gridgain 
Date:   2016-10-04T11:10:26Z

IGNITE-3597: Removed static work directory.

commit 1ab0650d60a67a39647446984f3a13227fe1dcb5
Author: Pavel Tupitsyn 
Date:   2016-10-05T13:09:49Z

IGNITE-4034 Get rid of specialized methods in platform targets

commit 9086a2933e9287c03498ceb13cc7410ea8831626
Author: Pavel Tupitsyn 
Date:   2016-10-05T13:40:59Z

Removing withAsync

commit 6fa73cf608c925692c69945c2372dc75e6befc7d
Author: Pavel Tupitsyn 
Date:   2016-10-05T13:54:18Z

Removing withAsync

commit e8308b027e16aa0766bab2300e4e55952bf2e80b
Author: Pavel Tupitsyn 
Date:   2016-10-05T14:05:42Z

removing with*

commit 6da753d8aaf39aeb8c3a6aaab025c84d3f454528
Author: Pavel Tupitsyn 
Date:   2016-10-05T14:15:05Z

removing with*

commit bec2eea724448306c8b56020bc5765e979c3ba6f
Author: Pavel Tupitsyn 
Date:   2016-10-05T14:24:59Z

removing with*

commit 4ecd240928b3bd50023bfcaec34106c40d553cf0
Author: Pavel Tupitsyn 
Date:   2016-10-05T14:57:34Z

Remove all custom methods from cache

commit 5c5ee9fe2255ce73c236c1fe23bb32579efa4959
Author: Pavel Tupitsyn 
Date:   2016-10-05T15:11:27Z

Remove all custom methods from cache

commit e84786ade13231c5d37f2b4de6de3e25ddccc125
Author: Pavel Tupitsyn 
Date:   2016-10-05T15:13:18Z

Remove all custom methods from cache

commit 1e0374f0c2df2714ea7b27da6323676076277c6c
Author: Pavel Tupitsyn 
Date:   2016-10-05T15:26:13Z

Remove all custom methods from cache

commit 5d4475799b313debca3a2eea68d9b89b656ceed0
Author: Pavel Tupitsyn 
Date:   2016-10-05T15:39:09Z

Remove all custom methods from cache

commit 4405a73be5fa88188b4391e10eef212c1dd9a1b1
Author: Pavel Tupitsyn 
Date:   2016-10-05T16:09:01Z

Fix cache methods in CPP




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---