Re: SELECT subqueries in DML statements

1. Actually this doc looks misleading and wrong to me. What does it mean "it will not be distributed"? It only means that we will not execute any distributed joins inside of this subquery. In all other means this operation will be correctly distributed. We will generate query like this : SELECT

Re: DML Documentation Readiness

Sure, will look into it. -P On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda wrote: > I’ve finished the review and released all the parts of DML documentation > [1]. > > Prachi, could you review whole SQL Grid documentation [2] including [1]? > Also it will be great if you check

EXPLAIN for DML statements

Alex P., Sergi, All we know that EXPLAIN is not supported for DML statements at the moment. http://apacheignite.gridgain.org/docs/dml#section-explain-support-for-dml-statements However, I can’t get how I can

SELECT subqueries in DML statements

Sergi, Presently in the DML statement doc we mention the following limitation related to SELECT subqueries http://apacheignite.gridgain.org/docs/dml#section-subqueries-in-where-clause Does it mean that this

Re: DML Documentation Readiness

I’ve finished the review and released all the parts of DML documentation [1]. Prachi, could you review whole SQL Grid documentation [2] including [1]? Also it will be great if you check this newly added section [3]. [1] http://apacheignite.gridgain.org/docs/dml

[GitHub] ignite pull request #1369: IGNITE-4439 - Attribute based node filter

Github user vkulichenko closed the pull request at: https://github.com/apache/ignite/pull/1369 --- 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: Node attribute filter

Thanks, Denis! Will merge shortly. On Thu, Dec 22, 2016 at 11:55 AM, Denis Magda wrote: > Val, thanks. Reviewed. Looks good to merge. > > — > Denis > > > On Dec 20, 2016, at 3:27 PM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > > Guys, > > > > I created

Re: Node attribute filter

Val, thanks. Reviewed. Looks good to merge. — Denis > On Dec 20, 2016, at 3:27 PM, Valentin Kulichenko > wrote: > > Guys, > > I created a simple implementation of IgnitePredicate based on > user attributes. This is the most commonly used approach for node

Re: Capacity Planning - Calculating Memory Usage

Alexandr, See my comments below. On Wed, Dec 21, 2016 at 7:01 PM, Alexandr Kuramshin wrote: > Hi Val, > > the understanding is simple. > > When you enables the single index on entry class you get "First index > overhead" per entry. > > When you enables two indices on

[jira] [Created] (IGNITE-4485) CacheJdbcPojoStore returns unexpected BinaryObject upon loadCache()

Alexandr Kuramshin created IGNITE-4485: -- Summary: CacheJdbcPojoStore returns unexpected BinaryObject upon loadCache() Key: IGNITE-4485 URL: https://issues.apache.org/jira/browse/IGNITE-4485

Re: Google Summer Of Code 2017

This is great! So, we already have three mentors in total (Val, Dmitriy, Denis). Anyone else? Any other tasks you think are suitable for this summer program? — Denis > On Dec 21, 2016, at 4:26 PM, Valentin Kulichenko > wrote: > > I can take over DataFrames

Re: Document issue

Hi, Do be honest I don’t see any issue there. Apache Ignite images for AWS and GCE run inside of a docker container. So the latest docker related commands look valid for me. Nick, please confirm. — Denis > On Dec 22, 2016, at 8:10 AM, 李玉珏@163 <18624049...@163.com> wrote: > > Hi， > > The

[jira] [Created] (IGNITE-4484) Call commit for read-only transactions.

Alexei Scherbakov created IGNITE-4484: - Summary: Call commit for read-only transactions. Key: IGNITE-4484 URL: https://issues.apache.org/jira/browse/IGNITE-4484 Project: Ignite Issue

[GitHub] ignite pull request #1378: IGNITE-1443: Minor fix.

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

Document issue

Hi， The following two pages of documents, more errors, I hope the community can be a comprehensive review, and then fix it. https://apacheignite.readme.io/docs/aws-deployment https://apacheignite.readme.io/docs/google-compute-deployment For example, under the two page, are all about docker

[GitHub] ignite pull request #1270: IGNITE-4063 BinaryType.fieldNames() should return...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1270 --- 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 #1323: IGNITE-4379: SQL: Local SQL field query broken in...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1323 --- 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 #1336: IGNITE-4264: Offheap cache entries statistics is ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1336 --- 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 #1379: gg 8.0.2.ea1

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

[jira] [Created] (IGNITE-4483) REST API - AtomicLong get/set/remove

Roman Bielik created IGNITE-4483: Summary: REST API - AtomicLong get/set/remove Key: IGNITE-4483 URL: https://issues.apache.org/jira/browse/IGNITE-4483 Project: Ignite Issue Type:

Re: Sort nodes in the ring in order to minimize the number of reconnections

Hello, Alex! I think it is a great idea. I suggest to build communications between nodes on weight (or priority). For example, ordering on latency: - nodes on one host = 1 - nodes in one rack-blade = 2 - nodes in one server-rack = 3 - nodes in one physical cluster = 4 - nodes in one subnet = 5

[GitHub] ignite pull request #1378: IGNITE-1443: Minor fix.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1378 IGNITE-1443: Minor fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1443 Alternatively you can review and

[GitHub] ignite pull request #1377: IGNITE-4471: Fixed ODBC string-reading utility fu...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1377 IGNITE-4471: Fixed ODBC string-reading utility function. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4471

[GitHub] ignite pull request #1376: Ignite gg 8.0.1.ea7 opt

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1376 Ignite gg 8.0.1.ea7 opt You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.1.ea7-opt Alternatively you

[jira] [Created] (IGNITE-4481) Part of IGNITE-4212

Oleg Ostanin created IGNITE-4481: Summary: Part of IGNITE-4212 Key: IGNITE-4481 URL: https://issues.apache.org/jira/browse/IGNITE-4481 Project: Ignite Issue Type: Sub-task

Re: Make async API great again

And several more improvements to future API: 1) Remove startTime() and duration() methods: https://issues.apache.org/jira/browse/IGNITE-4479 2) Fix broken cancellation semantics: https://issues.apache.org/jira/browse/IGNITE-4480 On Thu, Dec 22, 2016 at 1:40 PM, Vladimir Ozerov

[jira] [Created] (IGNITE-4480) Incorrect cancellation semantics in IgniteFuture.

Vladimir Ozerov created IGNITE-4480: --- Summary: Incorrect cancellation semantics in IgniteFuture. Key: IGNITE-4480 URL: https://issues.apache.org/jira/browse/IGNITE-4480 Project: Ignite

[jira] [Created] (IGNITE-4479) Remove startTime() and duration() methods from IgniteFuture

Vladimir Ozerov created IGNITE-4479: --- Summary: Remove startTime() and duration() methods from IgniteFuture Key: IGNITE-4479 URL: https://issues.apache.org/jira/browse/IGNITE-4479 Project: Ignite

Sort nodes in the ring in order to minimize the number of reconnections

Hello everyone, As far as I know nodes are connected in a ring. For example if i have 6 nodes, with names A, B, C, D, E, and F they can connect in ring any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, etc. And if some node falls out of topology neighboring nodes must reconnect. If nodes A,B and

[jira] [Created] (IGNITE-4478) Part of IGNITE-4212

Oleg Ostanin created IGNITE-4478: Summary: Part of IGNITE-4212 Key: IGNITE-4478 URL: https://issues.apache.org/jira/browse/IGNITE-4478 Project: Ignite Issue Type: Sub-task

Re: Make async API great again

Gents, I created tickets for all proposed improvements: 1) Nice async API: https://issues.apache.org/jira/browse/IGNITE-4475 2) Do not process IO messages synchronously for local node: https://issues.apache.org/jira/browse/IGNITE-4476 3) Better IgniteFuture API and callback semantics:

[jira] [Created] (IGNITE-4477) Fix IgniteFuture.listen() and IgniteFuture.chain() semantics

Vladimir Ozerov created IGNITE-4477: --- Summary: Fix IgniteFuture.listen() and IgniteFuture.chain() semantics Key: IGNITE-4477 URL: https://issues.apache.org/jira/browse/IGNITE-4477 Project: Ignite

[jira] [Created] (IGNITE-4476) GridIoManger must always process messages asynchronously

Vladimir Ozerov created IGNITE-4476: --- Summary: GridIoManger must always process messages asynchronously Key: IGNITE-4476 URL: https://issues.apache.org/jira/browse/IGNITE-4476 Project: Ignite

[jira] [Created] (IGNITE-4475) Simplify async API

Vladimir Ozerov created IGNITE-4475: --- Summary: Simplify async API Key: IGNITE-4475 URL: https://issues.apache.org/jira/browse/IGNITE-4475 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-4474) Ignite.createCache hangs on exception in CachePluginConfiguration.createProvider

Pavel Tupitsyn created IGNITE-4474: -- Summary: Ignite.createCache hangs on exception in CachePluginConfiguration.createProvider Key: IGNITE-4474 URL: https://issues.apache.org/jira/browse/IGNITE-4474

[jira] [Created] (IGNITE-4473) Client should re-try connection attempt in case of concurrent network failure

Vladimir Ozerov created IGNITE-4473: --- Summary: Client should re-try connection attempt in case of concurrent network failure Key: IGNITE-4473 URL: https://issues.apache.org/jira/browse/IGNITE-4473

[GitHub] ignite pull request #1374: Ignite 1.7.5

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

[GitHub] ignite pull request #1367: IGNITE-4248: Slf4jLogger ignores IGNITE_QUIET sys...

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

[GitHub] ignite pull request #1373: Ignite 4109

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