Re: Move documentation from readme.io to GitHub pages

Alexey, yes, cherry-pick to branches and update website for each version as well (this can be automated with a script) Still a bit cumbersome, but at least you don't have to make the same edit multiple times. On Fri, Feb 2, 2018 at 10:59 AM, Alexey Kuznetsov wrote: > Pavel, > > Do I correctly un

[GitHub] ignite pull request #3465: Ignite-7580

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/3465 Ignite-7580 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7580 Alternatively you can review and appl

Re: LOCAL cache on client

Sounds pretty reasonable for me, so fix will entail just in proper exception. Maybe it worth to show warning that says that's no data region configured and it's not possible to create LOCAL cache? Thanks! 02.02.2018 00:08, Valentin Kulichenko пишет: I meant "they should *explicitly* provide d

[GitHub] ignite pull request #3465: Ignite-7580

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

[GitHub] ignite pull request #3466: IGNITE-7580

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/3466 IGNITE-7580 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7580 Alternatively you can review and appl

[GitHub] ignite pull request #3466: IGNITE-7580

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

Re: [Review] IGNITE-4188: Savepoints support inside of Ignite Transactions

Hello! Semen, can you continue to review this ticket [1]? About my realisation: I added `savepoint()`, `rollbackToSavepoint()` and 'releaseSavepoint()' methods to `Transaction` interface. Savepoints are stored in `txState` of transaction on the initiator node and contain every change made since l

Re: Thin client failover mechanism (+ODBC, JDBC)

Pavel, Does it make sense in case of "connection lost" to ping available addresses in parallel? For example using thread pool of 4 threads? This may speed up detecting next alive node under Windows if several addresses become unavailable at once. On Fri, Feb 2, 2018 at 2:09 PM, Pavel Tupitsyn wr

Re: Thin client failover mechanism (+ODBC, JDBC)

Alexey, let's keep it simple for now. On Fri, Feb 2, 2018 at 11:47 AM, Alexey Kuznetsov wrote: > Pavel, > > Does it make sense in case of "connection lost" to ping available addresses > in parallel? > For example using thread pool of 4 threads? > This may speed up detecting next alive node under

Re: Ignite 3rd party support and employment page

Hi Denis, I think it is very interesting page, it may really help Ignite community to grow faster. Having this page new contributors will have information about companies, which requires Ignite expertise. Should we also mention EPAM here? As far as I now, a number of contributors works for EPAM.

[jira] [Created] (IGNITE-7610) Web Console: Refactor profile page to component

Alexey Kuznetsov created IGNITE-7610: Summary: Web Console: Refactor profile page to component Key: IGNITE-7610 URL: https://issues.apache.org/jira/browse/IGNITE-7610 Project: Ignite Issu

[jira] [Created] (IGNITE-7611) Document logger configuration options

Stanislav Lukyanov created IGNITE-7611: -- Summary: Document logger configuration options Key: IGNITE-7611 URL: https://issues.apache.org/jira/browse/IGNITE-7611 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7612) Web Console: Refactor mongo models creation.

Alexey Kuznetsov created IGNITE-7612: Summary: Web Console: Refactor mongo models creation. Key: IGNITE-7612 URL: https://issues.apache.org/jira/browse/IGNITE-7612 Project: Ignite Issue T

[jira] [Created] (IGNITE-7613) Unable to run example classes for JDK9 in IDEA

Sergey Kozlov created IGNITE-7613: - Summary: Unable to run example classes for JDK9 in IDEA Key: IGNITE-7613 URL: https://issues.apache.org/jira/browse/IGNITE-7613 Project: Ignite Issue Type:

Re: Move documentation from readme.io to GitHub pages

I noticed that Facebook open-sourced a documentation platform last month, https://docusaurus.io/, which may be worth considering. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #3467: .NET: Thin client: Add failover capability

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3467 .NET: Thin client: Add failover capability You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-7282 Alternatively you ca

Re: Eviction policies with persistence

Hi Val, I think it is quite accurate because eviction in case PDS enabled or not has quite different purposes. 1. Let us consider PDS enabled and page eviction occurs. First of all it is page based eviction, but not entry-based. Actually data is not removed, but only written to disk. We can addre

[jira] [Created] (IGNITE-7614) Documentation: How to access data from key-value that was inserted from SQL

Evgenii Zhuravlev created IGNITE-7614: - Summary: Documentation: How to access data from key-value that was inserted from SQL Key: IGNITE-7614 URL: https://issues.apache.org/jira/browse/IGNITE-7614

[jira] [Created] (IGNITE-7615) Find orphaned tests without test suites, create separate test suite for them

Ilya Kasnacheev created IGNITE-7615: --- Summary: Find orphaned tests without test suites, create separate test suite for them Key: IGNITE-7615 URL: https://issues.apache.org/jira/browse/IGNITE-7615 Pr

[jira] [Created] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.

Max Shonichev created IGNITE-7616: - Summary: GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration. Key: IGNITE-7616 URL: https://issues.apache.org

[jira] [Created] (IGNITE-7617) Contention on system.getProperty() in GridKernalContextImpl.isDaemon.

Andrew Mashenkov created IGNITE-7617: Summary: Contention on system.getProperty() in GridKernalContextImpl.isDaemon. Key: IGNITE-7617 URL: https://issues.apache.org/jira/browse/IGNITE-7617 Project

[GitHub] ignite pull request #3468: IGNITE-7508: Fix contention on system property ac...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3468 IGNITE-7508: Fix contention on system property access in GridKernalContextImpl::isDaemon() Fixed. You can merge this pull request into a Git repository by running: $ git pull https://githu

Re: Transport compression (not store compression)

Nikita, Yes, you're right. Maybe I wasn't clear enough. Usually server nodes are placed in the same fast network segment (one datacenter); in any case we need an ability to setup compression per connection using some filter like useCompression(ClusterNode, ClusterNode) to compress traffic only be

[GitHub] ignite pull request #3469: IGNITE-7606: delayed write during eviction

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3469 IGNITE-7606: delayed write during eviction IGNITE-7606: write evicted dirty page during eviction without holding segment write lock You can merge this pull request into a Git repository by runnin

Re: Transport compression (not store compression)

I think Igor is right. Ususally servers connected via fast local network. But clients could be in external and slow network. In this scenario compression will be very useful. Once I had such scenario - client connected to cluster via 300 kb/s network and tries to transfer ~10Mb of uncumpressed da

Re: LOCAL cache on client

Dmitry, I don't think we need to show warnings until there is an attempt to create a local cache. This is a very rare use case, not worth it. We should properly document it though. -Val On Fri, Feb 2, 2018 at 12:18 AM, Dmitry Karachentsev < dkarachent...@gridgain.com> wrote: > Sounds pretty rea

[jira] [Created] (IGNITE-7618) validateCache synchronously waits for state change

Alexey Goncharuk created IGNITE-7618: Summary: validateCache synchronously waits for state change Key: IGNITE-7618 URL: https://issues.apache.org/jira/browse/IGNITE-7618 Project: Ignite I

Re: Ignite 3rd party support and employment page

Makes sense, updated the page. Do we want to add a reference to the page to Ignite main page? If yes then where, any suggestions? For instance, Cassandra has a special “professionally supported” section for this purpose: http://cassandra.apache.org — Denis > On

Re: Eviction policies with persistence

Hi Guys, I agree with both Val and Dmitriy. Dmitriy is technically correct, but Val is also right that we should clean up the language. Here’s what I mean by "cleaning up the language": unless I’m missing something, eviction policy has no effect when Ignite persistence is enabled, because Igni

Re: Ignite SQL: How to drop table without explicit cache name

Guys, Right, first option is the way to go. Options 2 and 3 are surrogates that do not free you from concept of cache but rather allow you to obtain one. I believe in near future we'll propose public API for cacheless queries. - Alex 2018-02-01 19:38 GMT+03:00 Valentin Kulichenko : > Nikolay, >

Re: Eviction policies with persistence

Dmitriy, I’m surprised to hear that Random-LRU works at the entry level when Ignite persistence is off. Frankly, this section confuses a lot: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood#IgniteDurableMemory-underthehood-Entryeviction

Re: Move documentation from readme.io to GitHub pages

I think docusaurus.io could work for us. Denis, what do you think? On Fri, Feb 2, 2018 at 3:10 AM, endianignite wrote: > I noticed that Facebook open-sourced a documentation platform last month, > https://docusaurus.io/, which may be worth considering. > > > > > > -- > Sent from: http://apache-i

Re: Move documentation from readme.io to GitHub pages

Looks promising. Thanks for sharing. Updated the ticket. — Denis > On Feb 2, 2018, at 2:25 PM, Dmitriy Setrakyan wrote: > > I think docusaurus.io could work for us. Denis, what do you think? > > On Fri, Feb 2, 2018 at 3:10 AM, endianignite wrote: > >> I noticed that Facebook open-sourced a d

Re: Ignite 3rd party support and employment page

Denis, I think a link to this page should be added directly on the homepage. How about a short sentence right under the Benefits section? D. On Thu, Feb 1, 2018 at 4:25 PM, Denis Magda wrote: > Igniters, > > After clicking through various Apache sites and wikis, I discovered that > some project