Re: Move documentation from readme.io to GitHub pages

Pavel, Do I correctly understand, that if I find a typo in docs, I should commit fix to master and cherry-pick to all relevant branches? On Fri, Feb 2, 2018 at 2:28 PM, Pavel Tupitsyn wrote: > I did some research for my blog some time ago, and proposal is: > > * Export

Re: Move documentation from readme.io to GitHub pages

I did some research for my blog some time ago, and proposal is: * Export markdown from Readme.io (tweak as necessary, code samples etc) * Store markdown in git. Separate branch for each Ignite version (ignite-2.3-docs, ignite-2.4-docs, etc). Future version is in master. * Use Jekyll to generate

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

Dmitriy, yes, that's what I'm implementing as part of IGNITE-7282: * List of hosts in config * Pick random index (basic load balancing), connect * When connection is lost, all current requests throw an exception * Next request causes reconnect attempt to the next host * If all hosts fail, throw

[jira] [Created] (IGNITE-7609) .NET: FieldsQueryCursor should expose data types too

Pavel Tupitsyn created IGNITE-7609: -- Summary: .NET: FieldsQueryCursor should expose data types too Key: IGNITE-7609 URL: https://issues.apache.org/jira/browse/IGNITE-7609 Project: Ignite

[jira] [Created] (IGNITE-7608) Sort keys in putAll/removeAll methods

Alexander Belyak created IGNITE-7608: Summary: Sort keys in putAll/removeAll methods Key: IGNITE-7608 URL: https://issues.apache.org/jira/browse/IGNITE-7608 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7607) FieldsQueryCursor should expose data types too

Mikhail Cherkasov created IGNITE-7607: - Summary: FieldsQueryCursor should expose data types too Key: IGNITE-7607 URL: https://issues.apache.org/jira/browse/IGNITE-7607 Project: Ignite

Ignite 3rd party support and employment page

Igniters, After clicking through various Apache sites and wikis, I discovered that some projects such as Hadoop [2] and Cassandra [3] maintain the pages of 3rd parties that employ Apache experts and/or provide professional support. Eventually, I dared to assemble a similar page for Ignite [1].

Re: Upcoming Apache Ignite events this month

Great to see such a busy schedule! Ignite community is unstoppable :) D. On Thu, Feb 1, 2018 at 3:19 PM, Tom Diederich wrote: > Igniters, > > The following is a list of upcoming events in February. To view this list > from the Ignite events page, click here >

Upcoming Apache Ignite events this month

Igniters, The following is a list of upcoming events in February. To view this list from the Ignite events page, click here . Tokyo February 1: Meetup: Meet Apache Ignite In-Memory Computing Platform Join Roman Shtykh at the Tech it Easy- Tokyo

Re: Move documentation from readme.io to GitHub pages

Dmitriy, We will do a research before jumping off the readme.io train. In addition, to the technical issues outlined in the ticket, readme.io doesn’t give a way to tell Google “Hey, Google, index only the latest docs' version! Ignore specific versions”.

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

On Thu, Feb 1, 2018 at 5:55 AM, Pavel Tupitsyn wrote: > Ok, let's add simple reconnect logic and see what will come of it. > Just to clarify, a list of IP addresses a client should connect to needs to be provided on startup. Once a connection is lost, a client needs to try

Re: Move documentation from readme.io to GitHub pages

Guys, as I have been saying all along, we need to identify a documentation system we want to move to. Once we do that, we can plan how to move off of readme. Again, the most important benefit readme has is instantaneous documentation update. However, on the downside, they do not integrate with

Re: Orphaned, duplicate, and main-class tests!

Hi Ilya, Thank you for this research. I think it is useful for community to identify and remove obsolete tests (if any), and include lost test into CI run chain (if applicable). For test with main() methods I suggest to ask authors (git annotate) and if there is no response probably we should

Re: LOCAL cache on client

I meant "they should *explicitly* provide data region configuration", of course. -Val On Thu, Feb 1, 2018 at 10:58 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Agree with Mike. I don't think it's a good idea to implicitly create data > regions on client node. If one wants

Re: Eviction policies with persistence

Guys, Thanks for responses. But I still fail to understand how it affects a user. Are you saying that with persistence enabled Random-LRU is always used regardless of what is specified in pageEvictionMode, while in in-memory only scenario we can also utilize Random-2-LRU for eviction? Is this

Re: LOCAL cache on client

Agree with Mike. I don't think it's a good idea to implicitly create data regions on client node. If one wants to have a local there, they should implicitly provide data region configuration (default or otherwise). If data region is not configured, then we should throw proper exception instead of

Re: LOCAL cache on client

Hi Dmitry, I think we should make a user to explicitly create data region on a client. Client nodes aren't supposed to be used for data storing, so if someone what to use a local cache on a client node, let's make him/her create data region explicitly. Just to make sure that user knows what

Orphaned, duplicate, and main-class tests!

Hello! While working on Ignite, I have noticed that not all tests are in any test suite, hence I expect they are ignored. I have also noticed some files in src/test and named *Test.java are actually runnable main-classes and not tests. I think they're ignored to. Also I've noticed that 6 tests

[GitHub] ignite pull request #3464: Lost and Found suite for orphaned tests

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3464 Lost and Found suite for orphaned tests Remove duplicate tests. Mark abstract Abstract. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-7606) Write evicted dirty page during eviction without holding segment write lock

Dmitriy Pavlov created IGNITE-7606: -- Summary: Write evicted dirty page during eviction without holding segment write lock Key: IGNITE-7606 URL: https://issues.apache.org/jira/browse/IGNITE-7606

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

Nikolay, I believe the first option is the way to go. However, I'd also like to hear from other community members. Vladimir, Alex P, can you comment on this? I know we currently don't have public API to execute DDL statement without having a cache. However, looks like we use private API of

[GitHub] ignite pull request #3460: IGNITE-7599: Missed licenses in ignite-direct-io ...

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

[jira] [Created] (IGNITE-7605) SQL COPY: add more SQL parser tests for positive scenarios

Kirill Shirokov created IGNITE-7605: --- Summary: SQL COPY: add more SQL parser tests for positive scenarios Key: IGNITE-7605 URL: https://issues.apache.org/jira/browse/IGNITE-7605 Project: Ignite

LOCAL cache on client

Hello everyone! We have an erroneous use case when client tries to create LOCAL cache, but by default it does not initiates default data region. So client gets NPE. [1] I think it should be a lazy data region initialization on client. Do you have any concerns about this approach or other

[jira] [Created] (IGNITE-7604) SQL TX: Allow DML operations with reducer

Igor Seliverstov created IGNITE-7604: Summary: SQL TX: Allow DML operations with reducer Key: IGNITE-7604 URL: https://issues.apache.org/jira/browse/IGNITE-7604 Project: Ignite Issue

Re: Transport compression (not store compression)

Thanks for your comments, 1. At first, I would define final design and then I will make it pluggable. 2. We cannot prioritize messages at this network communication level. If compression utilizes processor poorly then we can increase count of selectors (make more threads when compression

[jira] [Created] (IGNITE-7603) Waiting on reconnect future doesn't lead to working instance when client reconnects

Ilya Kasnacheev created IGNITE-7603: --- Summary: Waiting on reconnect future doesn't lead to working instance when client reconnects Key: IGNITE-7603 URL: https://issues.apache.org/jira/browse/IGNITE-7603

Re: Move documentation from readme.io to GitHub pages

Good news, Denis. By the way, readme.io uses some kind of markdown dialect, and they have "export" feature, so it should be possible to move to some markdown-based system like Jekyll without too much hassle. On Thu, Feb 1, 2018 at 2:18 AM, Denis Magda wrote: > Created a

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

Ok, let's add simple reconnect logic and see what will come of it. On Thu, Feb 1, 2018 at 12:49 AM, Dmitriy Setrakyan wrote: > Pavel, > > I disagree. I think automatic reconnect is a very useful feature. For > example, all client-side operation can throw exception anyway,

[GitHub] ignite pull request #3463: IGNITE-7489 Factor total allocated pages in data ...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3463 IGNITE-7489 Factor total allocated pages in data region's fillFactor. … add test. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-7602) SQL COPY: add tests for file reading failures

Kirill Shirokov created IGNITE-7602: --- Summary: SQL COPY: add tests for file reading failures Key: IGNITE-7602 URL: https://issues.apache.org/jira/browse/IGNITE-7602 Project: Ignite Issue

Re: Stop nodes after test by default - IGNITE-6842

Hi Maxim, I would be happy if this issue is completed. I think best solultion is 1) to validate remained up and running nodes 2) and fail test if not-stopped nodes remained instead of silently stop node. If nodes will be stopped silently, probable errors may be missed both in test and in Ignite

Re: Eviction policies with persistence

Hi Vyacheslav, Yes, this is right, but for now PDS page based eviction uses Random-LRU, not Random-2-LRU. Something may be changed in future Ignite releases, but now Random-LRU is used. I am going to research if there is some room for improvements in this aspect (e.g. IGNITE-7507 recenly found).

[jira] [Created] (IGNITE-7601) SQL COPY: add tests for implicit columns (_key, _val, _ver)

Kirill Shirokov created IGNITE-7601: --- Summary: SQL COPY: add tests for implicit columns (_key, _val, _ver) Key: IGNITE-7601 URL: https://issues.apache.org/jira/browse/IGNITE-7601 Project: Ignite

[GitHub] ignite pull request #3462: Ignite 2.4.3

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

Ignite SQL: How to drop table without explicit cache name

Hello, guys. I working on support of saving Spark DataFrame to Ignite [1]. I want to execute "DROP TABLE XXX" query. To execute some SQL query in regulary way one need some cache. That cache has to differs from table cache to execute "DROP TABLE" successfully. I founded 3 different ways to

[GitHub] ignite pull request #3457: IGNITE-7561 .NET: Add IServices.GetDynamicService...

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

[GitHub] ignite pull request #3418: Ignite 6899 check

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

[GitHub] ignite pull request #3461: IGNITE-7309 Throw NodeStoppingException if marsha...

GitHub user gromtech opened a pull request: https://github.com/apache/ignite/pull/3461 IGNITE-7309 Throw NodeStoppingException if marshaling fails while node stopping * Wrapped error log (U.error) at GridJobWorker.onJobFinished to check node stopping * Add GridJobWorkerTest

[jira] [Created] (IGNITE-7600) visorcmd: add column 'type' for 'mlist' result

Pavel Konstantinov created IGNITE-7600: -- Summary: visorcmd: add column 'type' for 'mlist' result Key: IGNITE-7600 URL: https://issues.apache.org/jira/browse/IGNITE-7600 Project: Ignite

[GitHub] ignite pull request #3460: IGNITE-7599: Missed licenses in ignite-direct-io ...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3460 IGNITE-7599: Missed licenses in ignite-direct-io module You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7599

Re: Annoying extra steps for enabling metrics

Folks, .setEventsDisabled looks to be a good solution, since we will always call it like .setEventsDisabled(true). Calling .setEventsEnabled(false), since true is a default, looks odd to me. On Wed, Jan 31, 2018 at 11:02 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Alex, >

[GitHub] ignite pull request #3459: IGNITE-7590: Change example for decision trees

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

[jira] [Created] (IGNITE-7599) Missed licenses in apache-ignite-io module

Sergey Kozlov created IGNITE-7599: - Summary: Missed licenses in apache-ignite-io module Key: IGNITE-7599 URL: https://issues.apache.org/jira/browse/IGNITE-7599 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7598) SQL: INSERT requires you to specify the column names even if you are adding values for all the columns of the table

Roman Shtykh created IGNITE-7598: Summary: SQL: INSERT requires you to specify the column names even if you are adding values for all the columns of the table Key: IGNITE-7598 URL: