Re: IGNITE-7107 Apache Ignite RPM packages

I've added IEP document [1] with current packages design for overview. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-11%3A+Introduce+Apache+Ignite+delivery+in+RPM+and+DEB+packages -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Integration with Docker Hub official repositories

Hi, all! I’d like to initiate a process if integrating with Docker Hub on official level - as other Apache projects currently integrated (httpd / tomcat / maven / etc.). So I’ve created a task [1] and assigned to myself. Planning to introduce pull request to docker hub git repositories soon wit

Re: Rework locking architecture for MVCC and transactional SQL

Denis, Sorry, may be I was not clear enough - "tuple-approach" and "persistent approach" are the same. By "tuple" I mean a row stored inside a data block. Currently we store lock information in Java heap and proposal is to move it to data blocks. The main driver is memory - if there are a rows to

[GitHub] ignite pull request #3224: Ignite 2.1.9

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

[jira] [Created] (IGNITE-7199) Web Console: some improvments

Alexey Kuznetsov created IGNITE-7199: Summary: Web Console: some improvments Key: IGNITE-7199 URL: https://issues.apache.org/jira/browse/IGNITE-7199 Project: Ignite Issue Type: Improvemen

Re: Apache Ignite as a distributed processing back-ends

Those are the valid points. Personally, I would go for the beam-repo way because it will guarantee that the integration works as expected with every Beam release. This is for instance how Ignite is integrated with Camel, MyBatis, Zeppelin. Anyway, here is a ticket. Hope that an Ignite fellow wi

[jira] [Created] (IGNITE-7198) Integrate with Apache Beam

Denis Magda created IGNITE-7198: --- Summary: Integrate with Apache Beam Key: IGNITE-7198 URL: https://issues.apache.org/jira/browse/IGNITE-7198 Project: Ignite Issue Type: Task Repor

Re: How properly handle IgniteOOM

Hello Mikhail, This problem is related to the discussion around Ignite internal problems and their possible resolution: http://apache-ignite-developers.2346864.n4.nabble.com/Internal-problems-requiring-graceful-node-shutdown-reboot-etc-td24856.html

Updated invitation: RSVP now for Dec. 13 Bay Area In-Memory Computing Meetup! @ Wed Dec 13, 2017 8pm - 10pm (CST) (dev@ignite.apache.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20171214T02Z DTEND:20171214T04Z DTSTAMP:20171213T230118Z ORGANIZER;CN=GridGain Meetups (includes guest talks):mailto:gridgain.com_ci 4oqrn7b9ia4drtrurq004...

Re: CacheMetrics update and rolling upgrades.

Hello Pavel, Could you share the signature of the new metrics with us hear? The community will be happy to provide a feedback. What do you mean under the rolling upgrade? There is no such a feature in Ignite. — Denis > On Dec 13, 2017, at 8:22 AM, Pavel Pereslegin wrote: > > Hi, Igniters! >

Re: Rework locking architecture for MVCC and transactional SQL

Vladimir, Thanks for a throughout overview and proposal. > Also we could try employing tiered approach > 1) Try to keep everything in-memory to minimize writes to blocks > 2) Fallback to persistent lock data if certain threshold is reached. What are the benefits of the backed-by-persistence app

Re: Separate code paths for Java 8 and Java 9

Hi Andrey, If it is possible to resolve all mentioned issues with static code blocks, then this is definitely preferrable approach. Let's fix simple issues first and see what to do with complex ones. Notably: 1) https://issues.apache.org/jira/browse/IGNITE-6740 - this call is on a hot path, so ref

[GitHub] ignite pull request #3223: IGNITE-7189: Fixed ODBC table names in metadata

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3223 IGNITE-7189: Fixed ODBC table names in metadata You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7189 Alternative

Separate code paths for Java 8 and Java 9

Igniters, As [1] proposes, a couple of new modules with version-specific code should be created. While working on issues from [2] umbrella I saw no significant reasons to emerge separate modules; most requirements can be covered by tiny conditional code pieces in static init blocks of existing uti

How properly handle IgniteOOM

Hi all, I faced with a problem that if Ignite has no memory and IgniteOOM was thrown, there's no way to continues work with a cluster. You cannot remove some part of data to free some space because during removing Ignite tries to move pages to a free list and free list tries to acquire more pages

[GitHub] ignite pull request #3222: IGNITE-7197 Avoid NPE in serviced() by waiting on...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3222 IGNITE-7197 Avoid NPE in serviced() by waiting on latch. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7197 Alt

[GitHub] ignite pull request #3213: IGNITE-6495 performance measurement of decision t...

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

CacheMetrics update and rolling upgrades.

Hi, Igniters! I’m working on IGNITE-6333 [1] and I need to add two new metrics into CacheMetrics. As I see, versioning is not supported for now. Do I need to care about rolling upgrades? [1] https://issues.apache.org/jira/browse/IGNITE-6333

[jira] [Created] (IGNITE-7197) Premature access to services() causes NullPointerException

Ilya Kasnacheev created IGNITE-7197: --- Summary: Premature access to services() causes NullPointerException Key: IGNITE-7197 URL: https://issues.apache.org/jira/browse/IGNITE-7197 Project: Ignite

[jira] [Created] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches

Mikhail Cherkasov created IGNITE-7196: - Summary: Exchange can stuck and wait while new node restoring state from disk and starting caches Key: IGNITE-7196 URL: https://issues.apache.org/jira/browse/IGNITE-7196

[jira] [Created] (IGNITE-7195) GridToStringBuilder should limit large collections output to first N elements

Yakov Zhdanov created IGNITE-7195: - Summary: GridToStringBuilder should limit large collections output to first N elements Key: IGNITE-7195 URL: https://issues.apache.org/jira/browse/IGNITE-7195 Proje

[jira] [Created] (IGNITE-7194) Limit the number of collection elements printed in S.toString()

Alexey Goncharuk created IGNITE-7194: Summary: Limit the number of collection elements printed in S.toString() Key: IGNITE-7194 URL: https://issues.apache.org/jira/browse/IGNITE-7194 Project: Igni

[jira] [Created] (IGNITE-7193) IgniteReflectionFactory does not handle primitive data types.

Vyacheslav Koptilin created IGNITE-7193: --- Summary: IgniteReflectionFactory does not handle primitive data types. Key: IGNITE-7193 URL: https://issues.apache.org/jira/browse/IGNITE-7193 Project:

[jira] [Created] (IGNITE-7192) JDBC: support FQDN to multiple IPs during connection establishment

Alexey Popov created IGNITE-7192: Summary: JDBC: support FQDN to multiple IPs during connection establishment Key: IGNITE-7192 URL: https://issues.apache.org/jira/browse/IGNITE-7192 Project: Ignite

[GitHub] ignite pull request #3220: IGNITE-4191

GitHub user gvvinblade reopened a pull request: https://github.com/apache/ignite/pull/3220 IGNITE-4191 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4191 Alternatively you can review and apply the

[GitHub] ignite pull request #3220: IGNITE-4191

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

[jira] [Created] (IGNITE-7191) JDBC: set socket buffer to 64k by default

Alexey Popov created IGNITE-7191: Summary: JDBC: set socket buffer to 64k by default Key: IGNITE-7191 URL: https://issues.apache.org/jira/browse/IGNITE-7191 Project: Ignite Issue Type: Improv

[jira] [Created] (IGNITE-7190) Docker Hub official repository deployment

Peter Ivanov created IGNITE-7190: Summary: Docker Hub official repository deployment Key: IGNITE-7190 URL: https://issues.apache.org/jira/browse/IGNITE-7190 Project: Ignite Issue Type: New Fe

[jira] [Created] (IGNITE-7189) ODBC: ODBC return weird names for tables created with DDL

Igor Sapego created IGNITE-7189: --- Summary: ODBC: ODBC return weird names for tables created with DDL Key: IGNITE-7189 URL: https://issues.apache.org/jira/browse/IGNITE-7189 Project: Ignite Issu

[GitHub] ignite pull request #3221: Ignite gg 13200

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

[GitHub] ignite pull request #3220: IGNITE-4191

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

[GitHub] ignite pull request #3219: test baseline

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3219 test baseline You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9.9 Alternatively you can review and apply thes

[jira] [Created] (IGNITE-7187) SQL TX: Near caches support

Igor Seliverstov created IGNITE-7187: Summary: SQL TX: Near caches support Key: IGNITE-7187 URL: https://issues.apache.org/jira/browse/IGNITE-7187 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7188) SQL TX: Retry strategy on lock conflicts

Igor Seliverstov created IGNITE-7188: Summary: SQL TX: Retry strategy on lock conflicts Key: IGNITE-7188 URL: https://issues.apache.org/jira/browse/IGNITE-7188 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7186) SQL TX: Updates on backup nodes/Replicated caches support

Igor Seliverstov created IGNITE-7186: Summary: SQL TX: Updates on backup nodes/Replicated caches support Key: IGNITE-7186 URL: https://issues.apache.org/jira/browse/IGNITE-7186 Project: Ignite

[jira] [Created] (IGNITE-7184) SQL TX: Support optimistic transactions

Igor Seliverstov created IGNITE-7184: Summary: SQL TX: Support optimistic transactions Key: IGNITE-7184 URL: https://issues.apache.org/jira/browse/IGNITE-7184 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7185) SQL TX: Updates during rebalancing.

Igor Seliverstov created IGNITE-7185: Summary: SQL TX: Updates during rebalancing. Key: IGNITE-7185 URL: https://issues.apache.org/jira/browse/IGNITE-7185 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7183) SQL TX: Implicit transactions

Igor Seliverstov created IGNITE-7183: Summary: SQL TX: Implicit transactions Key: IGNITE-7183 URL: https://issues.apache.org/jira/browse/IGNITE-7183 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #3218: IGNITE-7079: Add examples for kNN classification ...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3218 IGNITE-7079: Add examples for kNN classification and for kNN regression 1. Added two examples 2. Improved LabeledDataset 3. Added tests for these improvements. 4. Added helper class to

[jira] [Created] (IGNITE-7182) Long sorting of pages collection on checkpoint begin can cause zero dropdown even with throttling enabled

Ivan Rakov created IGNITE-7182: -- Summary: Long sorting of pages collection on checkpoint begin can cause zero dropdown even with throttling enabled Key: IGNITE-7182 URL: https://issues.apache.org/jira/browse/IGNITE-7

[GitHub] ignite pull request #3115: IGNITE-6423: PDS could be corrupted if partition ...

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

[GitHub] ignite pull request #3217: IGNITE-7181 - Fix IGNITE-7086 doesn't work with P...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/3217 IGNITE-7181 - Fix IGNITE-7086 doesn't work with PESSIMISTIC REPEATABL… …E_READ transaction You can merge this pull request into a Git repository by running: $ git pull https://github

Rework locking architecture for MVCC and transactional SQL

Igniters, As you probably we know we work actively on MVCC [1] and transactional SQL [2] features which could be treated as a single huge improvement. We face a number of challenges and one of them is locking. At the moment information about all locks is kept in memory on per-entry basis (see Gri

IGNITE-1025 is ready for review (Need to print out warning if IP finder has a lot of addresses on Windows)

Hi, Igniters! I've prepared PR [1] for the issue IGNITE-1025 "Need to print out warning if IP finder has a lot of addresses on Windows" [2] . TeamCity tests look good [3]. Could someone review it? Thanks in advance! [1]https://github.com/apache/ignite/pull/2966 [2]https://issues.apache.org/jira/br

[jira] [Created] (IGNITE-7181) Fix IGNITE-7086 doesn't work with PESSIMISTIC REPEATABLE_READ transaction

Dmitry Karachentsev created IGNITE-7181: --- Summary: Fix IGNITE-7086 doesn't work with PESSIMISTIC REPEATABLE_READ transaction Key: IGNITE-7181 URL: https://issues.apache.org/jira/browse/IGNITE-7181

Re: IGNITE-4447 ready for review

Hello. Semyon, test passed. PR (squashed and merged with master): https://github.com/apache/ignite/pull/3204 CI tests: https://ci.ignite.apache.org/viewLog.html?buildId=993439&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteCache5 2017-05-19 4:46 GMT+03:00 Вадим Опольский : > Hi guys! > > S

[jira] [Created] (IGNITE-7180) ODBC: add possibility to configure more than one address in connection string

Evgenii Zhuravlev created IGNITE-7180: - Summary: ODBC: add possibility to configure more than one address in connection string Key: IGNITE-7180 URL: https://issues.apache.org/jira/browse/IGNITE-7180