Re[4]: Cache scan efficiency

Great, i don`t think about that. >Среда, 19 сентября 2018, 9:40 +03:00 от Vladimir Ozerov : > >Pinning is even worse thing, because you loose control on how data is moved >within a single region. Instead, I would suggest to use partition warmup + >separate data region to achieve "pinning" semanti

Unable to get the ignite cache metrics

Hi I am new to ignite. Brought up the ignite servers on k8s. Enabled the cache level metrics by setting the below property in ignite config xml for specific cache As part of Ignite client(brought up as another pod) i am putting the data into cache. when i checked the below cache metrics i am

[jira] [Created] (IGNITE-9641) Web console: inconsistent 'question' icon behaviour

Pavel Konstantinov created IGNITE-9641: -- Summary: Web console: inconsistent 'question' icon behaviour Key: IGNITE-9641 URL: https://issues.apache.org/jira/browse/IGNITE-9641 Project: Ignite

Re: Re[2]: Cache scan efficiency

Pinning is even worse thing, because you loose control on how data is moved within a single region. Instead, I would suggest to use partition warmup + separate data region to achieve "pinning" semantics. On Wed, Sep 19, 2018 at 8:34 AM Zhenya Stanilovsky wrote: > hi, but how to deal with page re

[GitHub] ignite pull request #4790: IGNITE-9627

GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/4790 IGNITE-9627 You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite ignite-9627 Alternatively you can review and apply these chan

Re[2]: Cache scan efficiency

hi, but how to deal with page replacements, which Dmitriy Pavlov mentioned? this approach would be efficient if all data fits into memory, may be better to have method to pin some critical caches? >Среда, 19 сентября 2018, 0:26 +03:00 от Dmitriy Pavlov : > >Even better, if RAM is exhausted page

[GitHub] ignite pull request #4789: Add TypeScript support to web console frontend

GitHub user Klaster1 opened a pull request: https://github.com/apache/ignite/pull/4789 Add TypeScript support to web console frontend You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9552 Alternative

Re: About work around for https://issues.apache.org/jira/browse/IGNITE-5795

I checked the source code just now and found *AffinityKey* is using *@AffinityKeyMapped* that's to say *AffinityKey* has the same issue. am I right? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

About work around for https://issues.apache.org/jira/browse/IGNITE-5795

I ran into the same issue as http://apache-ignite-users.70518.x6.nabble.com/SQL-SELECT-with-AffinityKeyMapped-no-results-td23141.html#a24232 from the document https://apacheignite.readme.io/docs/affinity-collocation, there are two ways to achieve *Affinity*. I would like to confirm that use *Aff

Re: Python thin client

Hi Dmitry, Not sure if you are aware but all documentation for the thin clients will be moved to readme.io. Here is the ticket for Python thin clients - https://issues.apache.org/jira/browse/IGNITE-9522 I am already working on it. So if you make any changes to the docs in your repo, please let me

Re: PHP thin client

Hi Stephan, Alexey That's exactly what readme.io contains - installation instructions, configuration, and examples for key-value, sql, etc. for thin clients. For example, see these documentation pages for Node.js (currently hidden in the latest version of the doc) : https://apacheignite.readme.io

Re: Cache scan efficiency

Even better, if RAM is exhausted page replacement process will be started. https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood#IgniteDurableMemory-underthehood-Pagereplacement(rotationwithdisk) Effect of the preloading will be still markable, but not as excell

Re: Cache scan efficiency

Agree, it's just a matter of the documentation. If a user stores 100% in RAM and on disk, and just wants to warm RAM up after a restart then he knows everything will fit there. If during the preloading we detect that the RAM is exhausted we can halt it and print out a warning. -- Denis On Tue, Se

Re: Cache scan efficiency

Hi, I totally support the idea of cache preload. IMO it can be expanded. We can iterate over local partitions of the cache group and preload each. But it should be really clear documented methods so a user can be aware of the benefits of such method (e.g. if RAM region is big enough, etc). Sinc

Re: Cache scan efficiency

Folks, Since we're adding a method that would preload a certain partition, can we add the one which will preload the whole cache? Ignite persistence users I've been working with look puzzled once they realize there is no way to warm up RAM after the restart. There are use cases that require this.

[GitHub] ignite pull request #4788: IGNITE-9514: Refactor tests and common test time

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/4788 IGNITE-9514: Refactor tests and common test time You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9514 Alternati

Re: Apache Ignite 2.7 release

Hi Paul. There are 2 PRs linked to that ticket. Who is reviewing your changes? Branch for 2.7 is still master, so if your changes are reviewed and accepted soon it will be in 2.7. Sincerely, Dmitriy Pavlov вт, 18 сент. 2018 г. в 16:22, Paul Anderson : > Hi, may I ask for IGNITE-9298 to be incl

Re: The future of Affinity / Topology concepts and possible PME optimizations.

Ilya, I would suggest that you discuss everything here on the dev@ list, including suggestions how to split the work. D. On Tue, Sep 18, 2018 at 6:34 PM Ilya Lantukh wrote: > Thanks for the feedback! > > I agree that we should start with the simplest optimizations, but it seems > that decouplin

Re: .net decimal -> Ignite is being stored as Other

Thanks, I was then incorrectly told to come here. On 18 Sep 2018, 17:21, at 17:21, Dmitriy Pavlov wrote: >Let me explain. User list intented for user and developers >communication. >Igniters monitor user list. And why should we hide answers to this >issue >from other users? > >The dev. list relat

Re: .net decimal -> Ignite is being stored as Other

Let me explain. User list intented for user and developers communication. Igniters monitor user list. And why should we hide answers to this issue from other users? The dev. list related to contribution-related questions. For example, if someone has PR fixing issue in the product. So he or she wil

Re: .net decimal -> Ignite is being stored as Other

Is this not the ignite dev user forum. I am programming tables in ignite so why do I need to go there when they always tell me to come here for dev related questions? The issue is code and likely ignites ability to map. Net decimal to java big decimal. I really don't think the user group is the

Re: .net decimal -> Ignite is being stored as Other

Hi, is it related to some contribution? If not, I propose u...@ignite.apache.org as a better place to ask. вт, 18 сент. 2018 г. в 18:43, wt : > i have the following class > > [QuerySqlField] > public int vd { get; set; } > [QuerySqlField] > public long sharesininde

.net decimal -> Ignite is being stored as Other

i have the following class [QuerySqlField] public int vd { get; set; } [QuerySqlField] public long sharesinindex { get; set; } [QuerySqlField] public string name { get; set; } [QuerySqlField] public string isin { get; set; } [

Re: The future of Affinity / Topology concepts and possible PME optimizations.

Thanks for the feedback! I agree that we should start with the simplest optimizations, but it seems that decoupling affinity/topology versions is necessary before we can make any progress here, and this is a rather complex change all over the code. If anyone wants to help, please contact me priva

[GitHub] ignite pull request #4787: IGNITE-9639 Flaky failure of SqlSystemViewsSelfTe...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/4787 IGNITE-9639 Flaky failure of SqlSystemViewsSelfTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-9639 A

[jira] [Created] (IGNITE-9640) [TC Bot] Determine repetitive failure types by analyzing build log

Andrey Kuznetsov created IGNITE-9640: Summary: [TC Bot] Determine repetitive failure types by analyzing build log Key: IGNITE-9640 URL: https://issues.apache.org/jira/browse/IGNITE-9640 Project: I

[GitHub] ignite pull request #4782: IGNITE-9631: Timeouts in ZookeeperDIscoverySpi te...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4782 ---

[jira] [Created] (IGNITE-9639) Flaky failure of SqlSystemViewsSelfTest

Aleksey Plekhanov created IGNITE-9639: - Summary: Flaky failure of SqlSystemViewsSelfTest Key: IGNITE-9639 URL: https://issues.apache.org/jira/browse/IGNITE-9639 Project: Ignite Issue Typ

Re: Exchange stucks while node restoring state from WAL

Igniters, I would like this issue to be part of release 2.7. There is not much time left considering that I will have to correct comments after the review. Will anyone help with review? PR: https://github.com/apache/ignite/pull/4520/files Upsource: https://reviews.ignite.apache.org/ignite/review

Re: The future of Affinity / Topology concepts and possible PME optimizations.

Ilya, > 3. Start node in baseline: both affinity and topology versions should be incremented, but it might be possible to optimize PME for such case and avoid cluster-wide freeze. Partition assignments for such node are already calculated, so we can simply put them all into MOVING state. However,

[GitHub] ignite pull request #4738: IGNITE-9330

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4738 ---

[GitHub] ignite pull request #4786: IGNITE-8570

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/4786 IGNITE-8570 You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-8570 Alternatively you can review and apply these changes as the

[GitHub] SomeFire opened a new pull request #13: Green table header for PRs without possible blockers

SomeFire opened a new pull request #13: Green table header for PRs without possible blockers URL: https://github.com/apache/ignite-teamcity-bot/pull/13 This is an automated message from the Apache Git Service. To respond to

Re: MTCGA: SqlSystemViewsSelfTest is flaky

Ok, I will take a look at this test tomorrow. вт, 18 сент. 2018 г. в 16:40, Alexey Goncharuk : > Igniters, > > I noticed a pretty high raise in the SqlSystemViewsSelfTest failure rate > recently [1]. There is a chance that the failure was introduced by another > SQL system view ticket [2]. > > A

MTCGA: SqlSystemViewsSelfTest is flaky

Igniters, I noticed a pretty high raise in the SqlSystemViewsSelfTest failure rate recently [1]. There is a chance that the failure was introduced by another SQL system view ticket [2]. Alexey, as an author of the change and the test, would you mind taking a look? The test failure looks simple (i

Re: The future of Affinity / Topology concepts and possible PME optimizations.

Ilya, This is a great idea, but before we can ultimately decouple the affinity version from the topology version, we need to fix a few things with baseline topology first. Currently the in-memory caches are not using the baseline topology. We are going to fix this as a part of IEP-4 Phase II (base

[jira] [Created] (IGNITE-9638) .Net: JVM keeps track of CLR Threads, even when they are finished

Ilya Kasnacheev created IGNITE-9638: --- Summary: .Net: JVM keeps track of CLR Threads, even when they are finished Key: IGNITE-9638 URL: https://issues.apache.org/jira/browse/IGNITE-9638 Project: Ign

Re: Apache Ignite 2.7 release

Hi, may I ask for IGNITE-9298 to be included in 2.7 pls On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov wrote: > Hello, folks. > > Thanks for the comments. > > I will follow them. > > В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет: > > Nikolay, > > > > 1) *Do not* create ignite-2.7 branc

Re: Using materialised views for queries with joins

Sven, Support of materialized views sounds like a huge project. I would not expect it to appear in Ignite soon. As far as I see you have problems with data collocation. If you can not store the original data in replicated caches, then these views will be huge as well and thus must be partitioned

[GitHub] ignite pull request #4753: IGNITE-9585 Error message sometimes refers nonexi...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4753 ---

Re: The future of Affinity / Topology concepts and possible PME optimizations.

Ilya, I like your idea. Let's create IEP and jira issues. I will be glad to take a part in this journey once we'll discuss every optimization in details. чт, 13 сент. 2018 г. в 22:51, Dmitriy Setrakyan : > Ilya, > > Thanks for the detailed explanation. Everything you suggested makes sense. > Ne

[GitHub] ignite pull request #4785: IGNITE-9550 Get operation returns null for a lost...

GitHub user ibessonov opened a pull request: https://github.com/apache/ignite/pull/4785 IGNITE-9550 Get operation returns null for a lost partition with READ_SAFE policy You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/a

[GitHub] ignite pull request #4749: IGNITE-9022: Changed class label output in SVM

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4749 ---

[GitHub] ignite pull request #4715: IGNITE-9158: Added Pipeline

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4715 ---

[jira] [Created] (IGNITE-9637) SQL: Add indexes to data load benchmarks

Pavel Kuznetsov created IGNITE-9637: --- Summary: SQL: Add indexes to data load benchmarks Key: IGNITE-9637 URL: https://issues.apache.org/jira/browse/IGNITE-9637 Project: Ignite Issue Type: B

[jira] [Created] (IGNITE-9636) CacheBaselineTopologyTest#testClusterActiveWhileBaselineChanging is flaky in master

Alexey Goncharuk created IGNITE-9636: Summary: CacheBaselineTopologyTest#testClusterActiveWhileBaselineChanging is flaky in master Key: IGNITE-9636 URL: https://issues.apache.org/jira/browse/IGNITE-9636

Re: Python thin client

Great job. Best Regards, Igor On Tue, Sep 18, 2018 at 11:35 AM Dmitry Melnichuk < dmitry.melnic...@nobitlost.com> wrote: > Igor, > > All examples are in 'ignite/modules/platforms/python/examples'. > > I put examples in separate Python files mostly to be able to > automatically confirm their ope

[jira] [Created] (IGNITE-9635) Eternal initial partition map exchange

Alexey Platonov created IGNITE-9635: --- Summary: Eternal initial partition map exchange Key: IGNITE-9635 URL: https://issues.apache.org/jira/browse/IGNITE-9635 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-9634) [ML] Trainers as pipeline parameters that can be varied

Aleksey Zinoviev created IGNITE-9634: Summary: [ML] Trainers as pipeline parameters that can be varied Key: IGNITE-9634 URL: https://issues.apache.org/jira/browse/IGNITE-9634 Project: Ignite

Re: [ML] [New Feature] Trainers as pipeline parameters that can be varied

I think it's great proposal, I've created a ticket https://issues.apache.org/jira/browse/IGNITE-9634 -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-9633) [ML] Hyperparameter tuning improvements umbrella ticket

Aleksey Zinoviev created IGNITE-9633: Summary: [ML] Hyperparameter tuning improvements umbrella ticket Key: IGNITE-9633 URL: https://issues.apache.org/jira/browse/IGNITE-9633 Project: Ignite

Re: Cache scan efficiency

On Tue, Sep 18, 2018 at 1:58 PM Alexei Scherbakov < alexey.scherbak...@gmail.com> wrote: > Summing up, I suggest adding new public > method IgniteCache.preloadPartition(partId). > > I will start preparing PR for IGNITE-8873 > if no more objection

Re: Apache Ignite 2.7 release

Hello, folks. Thanks for the comments. I will follow them. В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет: > Nikolay, > > 1) *Do not* create ignite-2.7 branch until we're not started preparation to > real 2.7. > Use some temporary branch for this check instead, eg. > ignite-2.7-release-

Re: Upsource lags and connection timeouts

Also, I see following on each resolve attempt. UpsourceRequestExceptionImpl: 108: Internal error: An error occurred during flushing data to database вт, 18 сент. 2018 г. в 13:56, Anton Vinogradov : > Folks, > > Who is responsible for Upsouce [1]? > I see a performance issues last week. > Can we

Re: Cache scan efficiency

Summing up, I suggest adding new public method IgniteCache.preloadPartition(partId). I will start preparing PR for IGNITE-8873 if no more objections follow. вт, 18 сент. 2018 г. в 10:50, Alexey Goncharuk : > Dmitriy, > > In my understanding,

Upsource lags and connection timeouts

Folks, Who is responsible for Upsouce [1]? I see a performance issues last week. Can we check Upsource health? [1] https://reviews.ignite.apache.org

[GitHub] ignite pull request #4784: IGNITE-9381 fix, reproducer were added

GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/4784 IGNITE-9381 fix, reproducer were added You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9381 Alternativel

[GitHub] ignite pull request #4783: Ignite 9309 a

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

Re: Apache Ignite 2.7 release

Nikolay, 1) *Do not* create ignite-2.7 branch until we're not started preparation to real 2.7. Use some temporary branch for this check instead, eg. ignite-2.7-release-test 2) Please make sure you'll not cause real release actions (maven release and so on). Perform only vote_* steps. 3) Make sur

Re: PHP thin client

> You know, I'm confused with all this documentation stuff... > For nodejs client all docs were moved from the repo to readme.io but the > readme.md keeps the installation instructions (duplicated with > readme.io). Probably, that's ok. > Will add similar short readme.md to the PHP PR. Its goo

Re: Apache Ignite 2.7 release

If it is an Ignite release, then it has to pass through the vote. If not, then you can do the test without publishing or uploading the release. D. On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov wrote: > Ok. > > In case of TC questions — ask me. > > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov

Re: Apache Ignite 2.7 release

Ok. In case of TC questions — ask me. > On 18 Sep 2018, at 13:16, Nikolay Izhikov wrote: > > Hello, Petr. > > I want to make ignite-2.7 branch today. > And execute release procedure based on this branch. > > However, ignite-2.7 branch will be copy of master until code freeze date. > > В Вт

Re: Apache Ignite 2.7 release

Hello, Petr. I want to make ignite-2.7 branch today. And execute release procedure based on this branch. However, ignite-2.7 branch will be copy of master until code freeze date. В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет: > Will it be just a test or there is already ignite-2.7 branch? >

[GitHub] ignite pull request #4782: IGNITE-9631: Timeouts in ZookeeperDIscoverySpi te...

GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/4782 IGNITE-9631: Timeouts in ZookeeperDIscoverySpi test suite You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9631

Re: Apache Ignite 2.7 release

Will it be just a test or there is already ignite-2.7 branch? Fabric removal related TC modifications are not ready yet, and code is not in master. > On 18 Sep 2018, at 13:07, Nikolay Izhikov wrote: > > Hello, Igniters. > > I want to start and release procedures and make an RC1 build. > >

Re: Apache Ignite 2.7 release

Hello, Igniters. I want to start and release procedures and make an RC1 build. It has a 2 intention: 1. I want to walk through all release steps to make sure they all works for me. So I will be fully ready on release date. 2. We have updated some dependencies in 2.7 and we need to make sure bin

[GitHub] ignite pull request #4781: IGNITE-9629 JDBCv2: supports types conversions at...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/4781 IGNITE-9629 JDBCv2: supports types conversions at the JdbcResultSet You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ig

[GitHub] ignite pull request #4780: IGNITE-9628 Avoid using sun.reflect.generics.refl...

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/4780 IGNITE-9628 Avoid using sun.reflect.generics.reflectiveObjects package in ML module in ML module. You can merge this pull request into a Git repository by running: $ git pull https://

[GitHub] ignite pull request #4778: IGNITE-9625 Fix ML javadoc

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4778 ---

[GitHub] ignite pull request #4714: IGNITE-9441 Do not fail on zero CRC check in last...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4714 ---

Re: PHP thin client

But now in PR we have no readme at all Agree with examples on readme.io, but other information (how to install, how to configurate, install from sources, basic description) may be in sources, it help a lot Or it also should be on readme.io? This question because in other platforms have readme exi

[jira] [Created] (IGNITE-9632) Add support of trivial IN-operation for partition extraction

Sergey Grimstad created IGNITE-9632: --- Summary: Add support of trivial IN-operation for partition extraction Key: IGNITE-9632 URL: https://issues.apache.org/jira/browse/IGNITE-9632 Project: Ignite

[jira] [Created] (IGNITE-9631) Timeouts in ZookeeperDIscoverySpi test suite

Alexey Platonov created IGNITE-9631: --- Summary: Timeouts in ZookeeperDIscoverySpi test suite Key: IGNITE-9631 URL: https://issues.apache.org/jira/browse/IGNITE-9631 Project: Ignite Issue Typ

[jira] [Created] (IGNITE-9630) Partitions intersection for AND condition of same key

Sergey Grimstad created IGNITE-9630: --- Summary: Partitions intersection for AND condition of same key Key: IGNITE-9630 URL: https://issues.apache.org/jira/browse/IGNITE-9630 Project: Ignite

Re: PHP thin client

> 1. Because finally the docs should not be in the repo (unfortunately) but > on readme.io. > There is a task for that: > https://issues.apache.org/jira/browse/IGNITE-9523 > Added the link in the jira. Ok > 2. Examples in readme.md are more like code snippets (mostly not big) > intended to he

Re: [MTCGA]: new failures in builds [1888723] needs to be handled

Hi, Dmitriy! Vladimir assured me in a private conversation that both API parity and MemoryMetrics fixes will be made soon. Thank you! -- Kind Regards Roman Kondakov On 17.09.2018 18:55, Dmitriy Pavlov wrote: Hi Roman Kondakov, Vladimir Ozerov, is it possible and is it reasonable to fix test

[jira] [Created] (IGNITE-9629) JDBCv2: JdbcThinResultSet must support types conversions

Taras Ledkov created IGNITE-9629: Summary: JDBCv2: JdbcThinResultSet must support types conversions Key: IGNITE-9629 URL: https://issues.apache.org/jira/browse/IGNITE-9629 Project: Ignite Iss

[jira] [Created] (IGNITE-9628) Java 9: ML module compilation failure

Peter Ivanov created IGNITE-9628: Summary: Java 9: ML module compilation failure Key: IGNITE-9628 URL: https://issues.apache.org/jira/browse/IGNITE-9628 Project: Ignite Issue Type: Task A

Re: PHP thin client

Hi Stepan, 1. Why exists second branches with all documentation? I mean they looks good together, why need to separate? Because finally the docs should not be in the repo (unfortunately) but on readme.io. There is a task for that: https://issues.apache.org/jira/browse/IGNITE-9523 Also, one

[GitHub] ignite pull request #4779: IGNITE-9162 fixing condition is added

GitHub user SGrimstad opened a pull request: https://github.com/apache/ignite/pull/4779 IGNITE-9162 fixing condition is added You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9162 Alternatively you c

[jira] [Created] (IGNITE-9627) TcpCommunicationSpiSkipMessageSendTest.testClientSegmented is flaky in master

Amelchev Nikita created IGNITE-9627: --- Summary: TcpCommunicationSpiSkipMessageSendTest.testClientSegmented is flaky in master Key: IGNITE-9627 URL: https://issues.apache.org/jira/browse/IGNITE-9627 P

[jira] [Created] (IGNITE-9626) Applying WAL updates ignores evicition policy

Pavel Vinokurov created IGNITE-9626: --- Summary: Applying WAL updates ignores evicition policy Key: IGNITE-9626 URL: https://issues.apache.org/jira/browse/IGNITE-9626 Project: Ignite Issue Ty

[GitHub] ignite pull request #4778: IGNITE-9625 Fix ML javadoc

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/4778 IGNITE-9625 Fix ML javadoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9625 Alternatively you can re

Re: Python thin client

Igor, All examples are in 'ignite/modules/platforms/python/examples'. I put examples in separate Python files mostly to be able to automatically confirm their operability. All the lengthy explanations and cross-references are in the main documentation: https://apache-ignite-binary-protocol-c

Re: ignite .net plugin for security

It will authenticate cluster nodes and clients as well as authorise cache permissions On 18 Sep 2018, 09:23, at 09:23, Pavel Tupitsyn wrote: >Hi, > >Can you please elaborate, what does the plugin do? > > >On Mon, Sep 17, 2018 at 10:49 PM wt wrote: > >> I have almost completed a plugin in java a

[jira] [Created] (IGNITE-9625) ML: Can't build ignite binaries because java doc exception

Stepan Pilschikov created IGNITE-9625: - Summary: ML: Can't build ignite binaries because java doc exception Key: IGNITE-9625 URL: https://issues.apache.org/jira/browse/IGNITE-9625 Project: Ignite

Re: ignite .net plugin for security

Hi, Can you please elaborate, what does the plugin do? On Mon, Sep 17, 2018 at 10:49 PM wt wrote: > I have almost completed a plugin in java and was wondering if this plugin > could be made available in .net. I have seen an example online (here - > > https://dzone.com/articles/implementing-ign

[GitHub] ignite pull request #4772: Refine CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT ...

Github user pavlukhin closed the pull request at: https://github.com/apache/ignite/pull/4772 ---

[GitHub] ignite pull request #4777: Refine CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT ...

GitHub user pavlukhin opened a pull request: https://github.com/apache/ignite/pull/4777 Refine CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT javadoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9624

Re: Cache scan efficiency

Dmitriy, In my understanding, the proper fix for the scan query looks like a big change and it is unlikely that we include it in Ignite 2.7. On the other hand, the method suggested by Alexei is quite simple and it definitely fits Ignite 2.7, which will provide a better user experience. Even havin

[jira] [Created] (IGNITE-9624) Refine CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT javadoc

Ivan Pavlukhin created IGNITE-9624: -- Summary: Refine CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT javadoc Key: IGNITE-9624 URL: https://issues.apache.org/jira/browse/IGNITE-9624 Project: Ignite

Re: PHP thin client

Sorry for interruption but im also review this feature and have couple questions about documentation 1. Why exists second branches with all documentation? I mean they looks good together, why need to separate? Also, one place when i found this branch it is this thread, not in jira, not in a github

[GitHub] asfgit closed pull request #12: Decode jira token

asfgit closed pull request #12: Decode jira token URL: https://github.com/apache/ignite-teamcity-bot/pull/12 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from

[GitHub] SomeFire opened a new pull request #12: Decode jira token

SomeFire opened a new pull request #12: Decode jira token URL: https://github.com/apache/ignite-teamcity-bot/pull/12 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub an