Re: .sha Release Distribution Policy

Hi, Denis Yes, we have a ticket that already takes this into account: https://issues.apache.org/jira/browse/IGNITE-5817 I think we can create both sha-256 and sha-512 checksums. Best regards Oleg On Thu, Aug 17, 2017 at 1:51 AM, Denis Magda wrote: > Igniters, especially the

[jira] [Created] (IGNITE-6093) SQL: Add hints support

Vladimir Ozerov created IGNITE-6093: --- Summary: SQL: Add hints support Key: IGNITE-6093 URL: https://issues.apache.org/jira/browse/IGNITE-6093 Project: Ignite Issue Type: Bug

Re: Batch service deployment

> Can we add an "allOrNone" flag to the deployment method? Sounds good, I think we can. > However, hot do you ensure atomicity here? We can guarantee that if some of configurations are invalid, or a transaction, that writes configuration to the internal cache, fails, then no services will be

[jira] [Created] (IGNITE-6094) Web console: Implement persistent store in demo mode.

Vasiliy Sisko created IGNITE-6094: - Summary: Web console: Implement persistent store in demo mode. Key: IGNITE-6094 URL: https://issues.apache.org/jira/browse/IGNITE-6094 Project: Ignite

[jira] [Created] (IGNITE-6095) Web console: In demo mode Implement configuration of key fields in domain model for SQL query

Vasiliy Sisko created IGNITE-6095: - Summary: Web console: In demo mode Implement configuration of key fields in domain model for SQL query Key: IGNITE-6095 URL: https://issues.apache.org/jira/browse/IGNITE-6095

[GitHub] ignite pull request #2079: IGNITE-5233: JDBC thin Driver: implement metadata...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2079 --- 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 #2463: IGNITE-6096 : Fixed races on partition evict.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2463 IGNITE-6096 : Fixed races on partition evict. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6096

The reason behind locking backup copy

Hi, Igntrs! Consider primary node P, backup node B for some key1. When we create lock on this key (at primary node) : IgniteCache primaryCache = primaryIgnite.cache(DEFAULT_CACHE_NAME); primaryCache.lock("key1").lock() After lock acquired on primary node, the

[GitHub] ignite pull request #2464: IGNITE-5849 metastorage

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

Re: Redesigning Ignite's site Look & Feel

Hello, try again now. This is hosted currently on my local machine until we move onto a staging server. > On 17 Aug 2017, at 02:58, Alexey Kuznetsov wrote: > > I cannot open this url. > It is working? > > On Thu, Aug 17, 2017 at 8:16 AM, Dmitriy Setrakyan

[jira] [Created] (IGNITE-6096) Race between partition eviction and re-creation

Ilya Lantukh created IGNITE-6096: Summary: Race between partition eviction and re-creation Key: IGNITE-6096 URL: https://issues.apache.org/jira/browse/IGNITE-6096 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6097) GridCacheDatabaseSharedManager.restorePartitionState(...) should not access PageMemory directly

Ilya Lantukh created IGNITE-6097: Summary: GridCacheDatabaseSharedManager.restorePartitionState(...) should not access PageMemory directly Key: IGNITE-6097 URL: https://issues.apache.org/jira/browse/IGNITE-6097

[GitHub] ignite pull request #2454: IGNITE-6080

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2454 --- 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

Re: .sha Release Distribution Policy

Denis Also we don't use .sha extension so we already follow that rules On Thu, Aug 17, 2017 at 10:57 AM, Oleg Ostanin wrote: > Hi, Denis > > Yes, we have a ticket that already takes this into account: > https://issues.apache.org/jira/browse/IGNITE-5817 > I think we can

Re: SQL Getting Started Guide

When I have the opportunity to test the ODBC code and ensure that it performs, I will add it to GH. At the moment, just snippets exist. If anyone can assist with this, I would appreciate it, as I have no experience with ODBC. I made some efforts to build the ODBC driver and have had some success

Re: IGNITE-5714 Context switching for pessimistic transactions

Aleksey, GridCacheTxFinishSync is used in IgniteTxManager#awaitFinishAckAsync() method (the wait is done before mapping Near or Colocated lock future, see the call hierarchy). --AG 2017-08-11 17:52 GMT+03:00 ALEKSEY KUZNETSOV : > Hi! > There is GridCacheTxFinishSync

[GitHub] ignite pull request #2458: IGNITE-GG-12549-1.9.6

Github user asfedotov closed the pull request at: https://github.com/apache/ignite/pull/2458 --- 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 #2462: IGNITE-6091 fix flaky test CacheLateAffinityAssig...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2462 --- 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 #2417: Ignite 5947

Github user ntikhonov closed the pull request at: https://github.com/apache/ignite/pull/2417 --- 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 #2393: IGNITE-5738: SQL: Added support for batching for ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2393 --- 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 #2270: IGNITE-5505 @AffinityKeyMapped annotation is igno...

Github user kukushal closed the pull request at: https://github.com/apache/ignite/pull/2270 --- 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

Re: SQL Getting Started Guide

Akmal, I work on the ODBC driver and would be glad to help. You can send mails with your requests to devlist and I will try to help as much as I can. Best Regards, Igor On Thu, Aug 17, 2017 at 3:28 PM, Akmal Chaudhri wrote: > When I have the opportunity to test

ERROR: Heuristic transaction failure.

Hello. We are trying to use the Ignite Memory File System and sometimes Ignite can't write file to IGFS and can't read. What is this happens? Below is an example for Cloudera Quick Start VM 5.10.0 and error, also configuration and full log in attachments. This problems arise on our cluster

[GitHub] ignite pull request #2345: IGNITE-5837 Test logic fix.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2345 --- 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

Re: IGNITE-5714 Context switching for pessimistic transactions

I cannot find\create an example test scenario where a thread waits on it. A thread can wait only if finish request had been sent and finish response had not been received. But it seems, lock cannot proceed mapping in this case. So, when lock call awaitFinishAckAsync, it is already done and thread

[jira] [Created] (IGNITE-6098) Test fail IgniteDataIntegrityTests.testExpandBuffer

Dmitriy Govorukhin created IGNITE-6098: -- Summary: Test fail IgniteDataIntegrityTests.testExpandBuffer Key: IGNITE-6098 URL: https://issues.apache.org/jira/browse/IGNITE-6098 Project: Ignite

[GitHub] ignite pull request #2441: IGNITE-6033 Add sorted and multithreaded modes in...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2441 --- 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 #2465: IGNITE-6098 fix test IgniteDataIntegrityTests.tes...

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/2465 IGNITE-6098 fix test IgniteDataIntegrityTests.testExpandBuffer You can merge this pull request into a Git repository by running: $ git pull

Re: IGNITE-5714 Context switching for pessimistic transactions

The problem is that GridCacheTxFinishSync stores thread id. When we call suspend on transaction, old thread id becames incorrect. So if this sync class is useless, we can eliminate thread id storage and this class. чт, 17 авг. 2017 г. в 15:47, ALEKSEY KUZNETSOV : > I

Re: new website tickets

Thanks Akmal, I’ve provide more details in the ticket. Let us know if you have any questions. — Denis > On Aug 17, 2017, at 11:51 AM, Akmal Chaudhri > wrote: > > I shall get started on this tomorrow. Hopefully finish it fairly quickly. > > Thank you. > > On 11

Re: Ignite Add-on/Extension Request: Please add GA Grid (beta) to Ignite website

Hi Turik, Sure, we will do this with pleasure. Prachi, could you add the component to the mentioned page? — Denis > On Aug 16, 2017, at 9:16 PM, techbysample wrote: > > Forum Admin, > > Please add project: > > GA Grid (beta): Distributive in Memory Genetic Algorithm

Re: How a new index is built in runtime?

Denis, you are absolutely right. Iterating through millions of objects is indeed a very complex task. Ignite casts a secret spell instead. --Yakov 2017-08-17 21:26 GMT+01:00 Denis Magda : > Alex P., Vladimir, > > Having CREATE INDEX command we can define indexes in runtime.

[GitHub] ignite pull request #2474: added throw runtime exception when mvcc addLocal

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2474 added throw runtime exception when mvcc addLocal You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5714-2 Alternatively you

[GitHub] ignite pull request #2475: added throw runtime exception when mvcc addLocal

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2475 added throw runtime exception when mvcc addLocal You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5714-3 Alternatively you

Re: .sha Release Distribution Policy

Guys, Thanks for the confirmation and taking care of this. — Denis > On Aug 17, 2017, at 1:32 AM, Sergey Kozlov wrote: > > Denis > > Also we don't use .sha extension so we already follow that rules > > On Thu, Aug 17, 2017 at 10:57 AM, Oleg Ostanin

Re: ERROR: Heuristic transaction failure.

Hi Usein, Which Java version do you have? There was a similar thread already where this exception was fixed by upgrading to the latest one:

Re: Failure to deserialize simple model object

Guys, Does anyone has ideas? -Val On Mon, Aug 14, 2017 at 4:33 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Cross-posting to dev > > Folks, > > I'm confused by the issue discussed in this thread. > > Here is the scenario: > - Start server node with a cache with POJO store

Re: SQL usability issues

No I see what you tried to convey. Here it is the doc: https://apacheignite.readme.io/docs/sql-tooling — Denis > On Aug 16, 2017, at 6:06 PM, Dmitriy Setrakyan wrote: > > Denis, > > I agree with Val. I am OK with using

[GitHub] ignite pull request #2473: added throw runtime exception when candidate add

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2473 added throw runtime exception when candidate add You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5714-1 Alternatively you

How a new index is built in runtime?

Alex P., Vladimir, Having CREATE INDEX command we can define indexes in runtime. However, it’s unclear how a new index is built. Let’s imagine I have a field “name” that was in Person’s model for a while and there are millions of such objects in the cluster. Now I turned the field into the

Re: Ignite2.1: Page eviction is not compatible with persistence when startup

Dmitriy, >> Developers, >> >> Let me bring this to your attention. Why do we throw an exception if the >> user has both an eviction policy and the Ignite persistence configured? Why >> don’t we simply ignore the eviction policy printing a warning and proceed >> with the node startup? >> > >

Re: Redesigning Ignite's site Look & Feel

Trying to request a staging server from INFRA: https://issues.apache.org/jira/browse/INFRA-14899 — Denis > On Aug 17, 2017, at 1:11 AM, Christos Erotocritou > wrote: > > Hello, try again now. This is hosted currently

Re: Redesigning Ignite's site Look & Feel

On Thu, Aug 17, 2017 at 1:45 PM, Denis Magda wrote: > Trying to request a staging server from INFRA: > https://issues.apache.org/jira/browse/INFRA-14899 < > https://issues.apache.org/jira/browse/INFRA-14899> > What is wrong with using Christos' laptop? :) > > — > Denis > >

[GitHub] ignite pull request #2476: Ignite-5983: Memory policy metrics should be avai...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/2476 Ignite-5983: Memory policy metrics should be available via REST. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-5983

Re: ODBC doc needs to be updated

Denis, it will be helpful to also file a ticket on this. On Thu, Aug 17, 2017 at 1:20 PM, Denis Magda wrote: > Hi Igor, > > Could you spend some time walking through the doc and updating it > considering the latest features and changes? >

Re: Default page size must be changed to 4k. Should it be backwards compatible?

On Tue, Aug 15, 2017 at 10:09 PM, Serge Puchnin wrote: > #1 option looks more predictable. But it's possible to add a message "for > better IO performance please migrate to 4K-pages". > Agree. Can we update the ticket to make sure that this suggestion is printed out?

Re: Ignite2.1: Page eviction is not compatible with persistence when startup

Agree. If we remove the exception though, we need to make sure to print out the warning that the eviction policy will be ignored with Ignite native persistence enabled. On Thu, Aug 17, 2017 at 1:35 PM, Denis Magda wrote: > Dmitriy, > > >> Developers, > >> > >> Let me bring

Re: Cluster auto activation design proposal

On Thu, Aug 17, 2017 at 7:34 AM, Sergey Chugunov wrote: > Dmitriy, > > As automatic creation of Baseline Topology is just another use case about > the whole concept, lets discuss it in this thread and forget about parallel > one. > > *initialActivationNodes* for

Re: Batch service deployment

Sounds good! Thanks for the detailed info. Can you please provide the updated API in the ticket? On Thu, Aug 17, 2017 at 12:41 AM, Denis Mekhanikov wrote: > > Can we add an "allOrNone" flag to the deployment method? > > Sounds good, I think we can. > > > However, hot do

[jira] [Created] (IGNITE-6105) Web console: Cache name is missed in preview for cache checkpoint SPI

Vasiliy Sisko created IGNITE-6105: - Summary: Web console: Cache name is missed in preview for cache checkpoint SPI Key: IGNITE-6105 URL: https://issues.apache.org/jira/browse/IGNITE-6105 Project:

Re: SQL usability issues

On Thu, Aug 17, 2017 at 2:22 PM, Denis Magda wrote: > No I see what you tried to convey. Here it is the doc: > https://apacheignite.readme.io/docs/sql-tooling < > https://apacheignite.readme.io/docs/sql-tooling> > Looks very nice. I think we should separate all the

Re: Ignite: configuration changes at runtime

On Thu, Aug 17, 2017 at 10:37 AM, Yakov Zhdanov wrote: > >I don't like the idea of intermixing changeable properties with constant > >ones in the configuration. Moreover, the standard configuration class is > >local to the node, while changing the config properties at

[jira] [Created] (IGNITE-6099) ODBC: Implement SQLGetInfo for all info types

Igor Sapego created IGNITE-6099: --- Summary: ODBC: Implement SQLGetInfo for all info types Key: IGNITE-6099 URL: https://issues.apache.org/jira/browse/IGNITE-6099 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6100) Test fail IgnitePdsRecoveryAfterFileCorruptionTest.testPageRecoveryAfterFileCorruption

Dmitriy Govorukhin created IGNITE-6100: -- Summary: Test fail IgnitePdsRecoveryAfterFileCorruptionTest.testPageRecoveryAfterFileCorruption Key: IGNITE-6100 URL:

[jira] [Created] (IGNITE-6102) Implement checks that node that joins topology has consistent database configuration

Ivan Rakov created IGNITE-6102: -- Summary: Implement checks that node that joins topology has consistent database configuration Key: IGNITE-6102 URL: https://issues.apache.org/jira/browse/IGNITE-6102

[GitHub] ignite pull request #2469: Ignite 6102

Github user glukos closed the pull request at: https://github.com/apache/ignite/pull/2469 --- 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 #2466: IGNITE-6100 fix memory leak

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2466 --- 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 #2468: IGNITE-3987: ODBC: Improved error output when que...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2468 IGNITE-3987: ODBC: Improved error output when query parsing failed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2437: IGNITE-5991

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2437 --- 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-6101) Try to improve local scans performance

Igor Seliverstov created IGNITE-6101: Summary: Try to improve local scans performance Key: IGNITE-6101 URL: https://issues.apache.org/jira/browse/IGNITE-6101 Project: Ignite Issue Type:

[GitHub] ignite pull request #2469: Ignite 6102

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

[GitHub] ignite pull request #2470: IGNITE-6102 Implement checks that node that joins...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2470 IGNITE-6102 Implement checks that node that joins topology has consistent database configuration You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2466: IGNITE-6100 fix memory leak

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/2466 IGNITE-6100 fix memory leak IgnitePdsRecoveryAfterFileCorruptionTest.testPageRecoveryAfterFileCorruption You can merge this pull request into a Git repository by running: $ git pull

Re: Cluster auto activation design proposal

Dmitriy, As automatic creation of Baseline Topology is just another use case about the whole concept, lets discuss it in this thread and forget about parallel one. *initialActivationNodes* for desired configuration of Baseline Topology sounds good to me, I would like to hear from other Igniters.

[GitHub] ignite pull request #2470: IGNITE-6102 Implement checks that node that joins...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2470 --- 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 #2463: IGNITE-6096 : Fixed races on partition evict.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2463 --- 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-6104) Web Console: move "Download Web Agent" link to footer.

Alexey Kuznetsov created IGNITE-6104: Summary: Web Console: move "Download Web Agent" link to footer. Key: IGNITE-6104 URL: https://issues.apache.org/jira/browse/IGNITE-6104 Project: Ignite

[GitHub] ignite pull request #2471: 8.0.3.ea15

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/2471 8.0.3.ea15 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.3.ea15 Alternatively you can review and

Re: How a new index is built in runtime?

On Thu, Aug 17, 2017 at 1:47 PM, Yakov Zhdanov wrote: > Denis, you are absolutely right. Iterating through millions of objects is > indeed a very complex task. Ignite casts a secret spell instead.\ > Well, Ignite should cast a secret spell and do it in parallel, across

[GitHub] ignite pull request #2467: added throw runtime exception when it waits on Gr...

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2467 added throw runtime exception when it waits on GridCacheTxFinishSync You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite

[jira] [Created] (IGNITE-6103) Handle -1 partition ID during WAL replay

Alexey Goncharuk created IGNITE-6103: Summary: Handle -1 partition ID during WAL replay Key: IGNITE-6103 URL: https://issues.apache.org/jira/browse/IGNITE-6103 Project: Ignite Issue

Re: Ignite: configuration changes at runtime

>I don't like the idea of intermixing changeable properties with constant >ones in the configuration. Moreover, the standard configuration class is >local to the node, while changing the config properties at runtime may be a >distributed operation that needs to be propagated across the cluster. I

[GitHub] ignite pull request #2472: Ignite 1.9.6

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

Re: new website tickets

I shall get started on this tomorrow. Hopefully finish it fairly quickly. Thank you. On 11 August 2017 at 20:45, Denis Magda wrote: > Akmal, > > Thanks for stepping in! Considering that you’ve been working on the SQL > getting started, I’ve reassigned the general getting

Re: SQL Getting Started Guide

Igor, Would you mind helping us to test the snippets? I do believe it will take you a couple of minutes since the environment is set up on your side. — Denis > On Aug 17, 2017, at 5:37 AM, Igor Sapego wrote: > > Akmal, > > I work on the ODBC driver and would be glad to

ODBC doc needs to be updated

Hi Igor, Could you spend some time walking through the doc and updating it considering the latest features and changes? https://apacheignite.readme.io/docs/quering-data For instance: 1. The configuration section [1] can be switched to the