Re: Ignite: configuration changes at runtime

Yakov, Very cool feature. I would also add to CacheConfiguration: StatisticsEnabled: on / off QueryDetailMetricsSize: change size Please also implement an API that could be used from UI tools (Web Console and Visor Cmd). On Fri, Aug 11, 2017 at 10:49 PM, Yakov Zhdanov

[jira] [Created] (IGNITE-6044) SQL insert waits for transaction commit, but it must be executed right away

Mikhail Cherkasov created IGNITE-6044: - Summary: SQL insert waits for transaction commit, but it must be executed right away Key: IGNITE-6044 URL: https://issues.apache.org/jira/browse/IGNITE-6044

Re: [jira] [Commented] (IGNITE-6026) init cluster for Ignite Persistence by xml

Hi Alex, Please specify "--port 11211" port when running "control.sh --activate". Also, add --host IGNITE_NODE if you run control.sh on a host where there are no ignite nodes. For example: ./bin/control.sh --host 127.0.0.1 --port 11211 --activate It looks we have an issue that default Ignite

Re: Hibernate dialect for Ignite

I think that's a great idea. Although I doubt anyone aver tried to use Ignite with Hibernate this way, so we need to do some testing first to identify limitations/issues we have there. -Val On Wed, Aug 9, 2017 at 12:58 PM, Dmitriy Setrakyan wrote: > Igniters, > > Given

Re: Ignite: configuration changes at runtime

Yakov, I like the idea, but I am not sure how we will separate properties that are dynamically changeable from the constant ones. Also, what is the API for updating these properties? Perhaps we can create a special interface, e.g. IgniteConfigurationRuntime (similar to Java Runtime class), which

Re: SQL Getting Started Guide

Denis, All I have made some progress with the documentation: https://apacheignite.readme.io/v2.1/docs/getting-started-sql ODBC connectivity and examples are missing, but should be completed very soon. Community feedback welcome. Thanks. On 31 July 2017 at 19:02, Denis Magda

Re: new website tickets

Dimitriy, I will take a look at those and pick-up the documentation tickets early next week. Thanks. On 11 August 2017 at 02:34, Dmitriy Setrakyan wrote: > Igniters, > > I have filed several website tickets to reflect the addition of persistence > in the latest 2.1

Updated Invitation: GoToWebinar - Introduction to Apache Ignite, a memory-cen... @ Wed Aug 16, 2017 12am - 1am (PDT) (dev@ignite.apache.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20170816T07Z DTEND:20170816T08Z DTSTAMP:20170811T182806Z ORGANIZER;CN=dma...@gridgain.com:mailto:dma...@gridgain.com

[jira] [Created] (IGNITE-6045) Hibernate dialect for Ignite

Dmitriy Setrakyan created IGNITE-6045: - Summary: Hibernate dialect for Ignite Key: IGNITE-6045 URL: https://issues.apache.org/jira/browse/IGNITE-6045 Project: Ignite Issue Type: Wish

[jira] [Created] (IGNITE-6043) Fix GridCacheSemaphoreImpl methods semantics

Andrey Kuznetsov created IGNITE-6043: Summary: Fix GridCacheSemaphoreImpl methods semantics Key: IGNITE-6043 URL: https://issues.apache.org/jira/browse/IGNITE-6043 Project: Ignite Issue

[GitHub] ignite pull request #2434: IGNITE-6009: Fixed IgniteSemaphore test.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2434 IGNITE-6009: Fixed IgniteSemaphore test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6009

[GitHub] ignite pull request #2435: Ignite 4756

GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2435 Ignite 4756 Added printDistribution method and AbstractAffinityFunctionSelfTest. You can merge this pull request into a Git repository by running: $ git pull

Re: Data compression in Ignite

Ivan, your points definitely make sense, however, I see at list one issue compared to per-page approach. With per-page we can split page to compressed and uncompressed regions and change the dictionary if more efficient compression is possible. With bigger areas such as partition or entire cache

[GitHub] ignite pull request #2427: Ignite 4756

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

Re: IgniteUtils#currentTimeMillis

Well, then let's leave it as is for now. --Yakov

[GitHub] ignite pull request #2433: Ignite 1.7.4 p3

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

Design proposal: automatic creation of BaselineTopology

Folks, As we are getting to the conclusion on the discussion about cluster automatic activation proposal [1] I would like to propose one more thing that may also be useful here. In addition to options of creating BLT (BTW, any ideas of a better name for the concept are welcome; feel free to send

Re: Cluster auto activation design proposal

More options to name the concept (one may put "node set" or "topology" at the end - for me these are interchangeable): 1. essential 2. basic 3. completed 4. prepared 5. solid 6. enduring To me the name must stress the fact that "node set" or "topology" contains all nodes user

Ignite integrations

Igniters, I have reviewed the Ignite integrations page, and it looks like most integrations are stuck on 1.9 version: https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations We should upgrade them to the latest release. Andrey Gura, can you please comment? D.

Re: new website tickets

Akmal, Thanks for stepping in! Considering that you’ve been working on the SQL getting started, I’ve reassigned the general getting guide task on you and provide more details and suggestions for it: https://issues.apache.org/jira/browse/IGNITE-6041

Re: SQL Getting Started Guide

Akmal, Good start! Please consider the following feedback: 1. Connectivity section. Emphasize that ignite-core.jar has to be copied to the classpath of an app or tool and give a link to more advanced JDBC Thin driver documentation if the one needs more details. Probably, similar steps should

SQL usability issues

Igniters, I have tried to connect to Ignite from DBeaver [1], and realized that there are some usability issues we need to address before the next release: 1. We need to have documentation on how to configure JDBC and ODBC drivers with external SQL tools [2] 2. You cannot highlight

Re: Cluster auto activation design proposal

Sergey, As it is becoming clear from another thread, the only configuration users will need to provide is the initial set of nodes. Everything else will be handled by Ignite automatically. In this case, the name Baseline Topology will appear only in documentation, in which case the name is OK

Re: Data compression in Ignite

I still don't understand per-partition compression, which is only local. How do entries get updated in the middle of a partition file? D. On Fri, Aug 11, 2017 at 3:44 AM, Yakov Zhdanov wrote: > Ivan, your points definitely make sense, however, I see at list one issue >

[jira] [Created] (IGNITE-6046) Multiple SQL statements in one command do not work

Dmitriy Setrakyan created IGNITE-6046: - Summary: Multiple SQL statements in one command do not work Key: IGNITE-6046 URL: https://issues.apache.org/jira/browse/IGNITE-6046 Project: Ignite

[jira] [Created] (IGNITE-6047) Need to support "show" SQL commands

Dmitriy Setrakyan created IGNITE-6047: - Summary: Need to support "show" SQL commands Key: IGNITE-6047 URL: https://issues.apache.org/jira/browse/IGNITE-6047 Project: Ignite Issue Type:

Re: Design proposal: automatic creation of BaselineTopology

I would call the setter setBaselineTopology, without the word Descriptor. Also, perhaps this BaselineTopology should be a standard predicate, just like the Node Filter we already have for ClusterGroup, so users could provide a custom cluster initialization logic. We, of course, should provide a

Re: SQL usability issues

Dmitriy, That's the documentation that shows how to configure Pentaho via JDBC: https://apacheignite-tools.readme.io/v2.1/docs/pentaho Plus on the tools' domain you can see Tableau based ODBC example. So, I'm not sure we need something else from the documentation standpoint. I would rather add

[jira] [Created] (IGNITE-6048) Need to document how to connect to Ignite from external SQL tools

Dmitriy Setrakyan created IGNITE-6048: - Summary: Need to document how to connect to Ignite from external SQL tools Key: IGNITE-6048 URL: https://issues.apache.org/jira/browse/IGNITE-6048 Project:

Re: IGNITE-5714 Context switching for pessimistic transactions

Hi! There is GridCacheTxFinishSync synchronizer, which used to notify threads (waiting on GridCacheTxFinishSync.TxFinishSync#pendingFut) that GridNearTxFinishResponse is received. Currently, only GridCacheTxFinishSync uses the synchronizer(but doesn't wait on it somehow). And it seems the

Re: new website tickets

On Fri, Aug 11, 2017 at 10:38 AM, Akmal Chaudhri < akmal.chaud...@gridgain.com> wrote: > Dimitriy, > > I will take a look at those and pick-up the documentation tickets early > next week. > > Awesome! Feel free to assign any tickets to yourself. > Thanks. > > On 11 August 2017 at 02:34, Dmitriy

Invitation: GoToWebinar - Introduction to Apache Ignite, a memory-cen... @ Wed Aug 16, 2017 12am - 1am (PDT) (dev@ignite.apache.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20170816T07Z DTEND:20170816T08Z DTSTAMP:20170811T182601Z ORGANIZER;CN=dma...@gridgain.com:mailto:dma...@gridgain.com

Re: Hibernate dialect for Ignite

I filed a ticket: https://issues.apache.org/jira/browse/IGNITE-6045 Maybe someone in the community will pick it up. D. On Fri, Aug 11, 2017 at 11:14 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > I think that's a great idea. Although I doubt anyone aver tried to use > Ignite

Ignite: configuration changes at runtime

Hello Igniters! I want to start a discussion on a pretty useful feature that will help us to bring Ignite's usability to the next level. How about supporting changes to (some) configuration at runtime? Currently, most of the config props are carved in stone and will require node restart for a