Re: Dedicated readme.io documentation for Ignite integrations

On Thu, Dec 1, 2016 at 10:28 AM, Denis Magda wrote: > I don't say we need it but rather mean that it’s still being delivered as > a part of the distribution. > > Let’s sweep it out once the Web Console based approach is documented >

Re: Dedicated readme.io documentation for Ignite integrations

I don't say we need it but rather mean that it’s still being delivered as a part of the distribution. Let’s sweep it out once the Web Console based approach is documented https://issues.apache.org/jira/browse/IGNITE-4349 — Denis > On Nov 30,

[jira] [Created] (IGNITE-4349) Discontinue the schema-import utility

Denis Magda created IGNITE-4349: --- Summary: Discontinue the schema-import utility Key: IGNITE-4349 URL: https://issues.apache.org/jira/browse/IGNITE-4349 Project: Ignite Issue Type: Task

Re: ignite-spark module in Hadoop Accelerator

Guys, I just downloaded the hadoop accelerator and here are the differences from the fabric edition that jump at me right away: - the "bin/" folder has "setup-hadoop" scripts - the "config/" folder has "hadoop" subfolder with necessary hadoop-related configuration - the "lib/" folder

Re: ignite-spark module in Hadoop Accelerator

Vovan, As one of hadoop maintainers, please share your point of view on this. — Denis > On Nov 30, 2016, at 10:49 PM, Sergey Kozlov wrote: > > Denis > > I agree that at the moment there's no reason to split into fabric and > hadoop editions. > > On Thu, Dec 1, 2016 at

Re: Dedicated readme.io documentation for Ignite integrations

Hi +1 for removing of schema import. On Thu, Dec 1, 2016 at 8:51 AM, Dmitriy Setrakyan wrote: > On Thu, Dec 1, 2016 at 8:10 AM, Denis Magda wrote: > > > Yes, sure, the schema-import utility is still being used and maintained. > > > > Why do we need

Re: ignite-spark module in Hadoop Accelerator

Denis I agree that at the moment there's no reason to split into fabric and hadoop editions. On Thu, Dec 1, 2016 at 4:45 AM, Denis Magda wrote: > Hadoop Accelerator doesn’t require any additional libraries in compare to > those we have in the fabric build. It only lacks some

Re: Dedicated readme.io documentation for Ignite integrations

On Thu, Dec 1, 2016 at 8:10 AM, Denis Magda wrote: > Yes, sure, the schema-import utility is still being used and maintained. > Why do we need it? > > I would create a separate page for Web Console for now and discontinue the > schema-import utility only when Web Console is

Re: Dedicated readme.io documentation for Ignite integrations

Yes, sure, the schema-import utility is still being used and maintained. I would create a separate page for Web Console for now and discontinue the schema-import utility only when Web Console is no longer in the beta state https://issues.apache.org/jira/browse/IGNITE-4348

[jira] [Created] (IGNITE-4348) Documentation: RDBMS Integration using Web Console

Denis Magda created IGNITE-4348: --- Summary: Documentation: RDBMS Integration using Web Console Key: IGNITE-4348 URL: https://issues.apache.org/jira/browse/IGNITE-4348 Project: Ignite Issue

Re: ignite-spark module in Hadoop Accelerator

Hadoop Accelerator doesn’t require any additional libraries in compare to those we have in the fabric build. It only lacks some of them as Val mentioned below. Wouldn’t it better to discontinue Hadoop Accelerator edition and simply deliver hadoop jar and its configs as a part of the fabric? —

Re: Dedicated readme.io documentation for Ignite integrations

Dmitriy, Agree. The documentation is already there. https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence However, the documentation is presently based on the legacy schema-import tool. It’s reasonable to refine

Re: Talking to Ignite From PHP

Igor, Finally, I could set up the PHP PDO environment and execute the queries, provided in the guidance [1]. However, I’ve faced with a couple of the issue that should be addressed as a part of 1.8 https://issues.apache.org/jira/browse/IGNITE-4347

Re: Apache Ignite 1.8 Release

I’ve faced with two more issues while was working with Ignite from PHP PDO side. The first one is related to DML. DML and PHP PDO: double field is converted to bigdecimal Alexander P. and Igor S. please pull together and fix this issue before

[jira] [Created] (IGNITE-4347) ODBC: NPE when cache name is different from the one configured in DSN

Denis Magda created IGNITE-4347: --- Summary: ODBC: NPE when cache name is different from the one configured in DSN Key: IGNITE-4347 URL: https://issues.apache.org/jira/browse/IGNITE-4347 Project: Ignite

[jira] [Created] (IGNITE-4346) DML and PHP PDO: double field is converted to bigdecimal

Denis Magda created IGNITE-4346: --- Summary: DML and PHP PDO: double field is converted to bigdecimal Key: IGNITE-4346 URL: https://issues.apache.org/jira/browse/IGNITE-4346 Project: Ignite

Re: Apache Ignite 1.8 Release

Hi Update for DML testing: IGNITE-4342 DML: clear() on atomic cache causes the exception from previous failed DML statement On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda wrote: > Vladimir, > > Please add to the release

Re: Cassandra basic setup

Regarding *cassandra-bootstrap.sh *and* ignite-bootstrap.sh* current documentation is up to date. These scripts are not automatically updated during release packaging process, according to the documentation (item 5 of *Configuration Details* section,

Locking of partition with affinityRun/affinityCall

Taras, There is a question in regards to the feature contributed by you recently https://issues.apache.org/jira/browse/IGNITE-2310 The Java API doc says that the partition will not be migrated while a job is being executed on a target node.

Re: Apache Ignite 1.8 Release

Vladimir, Please add to the release notes information regarding this feature https://issues.apache.org/jira/browse/IGNITE-2310 Essentially, it allows locking a partition while a remote computation is being executed on a node. I’ve already

Fwd: [jira] [Created] (IGNITE-4345) incorrect/outdated info on site

Nick, please handle the rest of Docker related issues referring to the discussion in the ticket. — Denis > Begin forwarded message: > > From: "Sergey Korzhevsky (JIRA)" > Subject: [jira] [Created] (IGNITE-4345) incorrect/outdated info on site > Date: November 30, 2016 at

[jira] [Created] (IGNITE-4345) incorrect/outdated info on site

Sergey Korzhevsky created IGNITE-4345: - Summary: incorrect/outdated info on site Key: IGNITE-4345 URL: https://issues.apache.org/jira/browse/IGNITE-4345 Project: Ignite Issue Type: Bug

Re: Cassandra basic setup

Cross-posting to the dev list. Igor R., is this something that has to be fixed for 1.8 as well? The community is planning to send the new release for vote by the end of Friday, could you look into this issue by that time? — Denis > On Nov 30, 2016, at 3:00 AM, Riccardo Iacomini

[jira] [Created] (IGNITE-4344) Client node allocates off heap memories for caches

Nikolay Tikhonov created IGNITE-4344: Summary: Client node allocates off heap memories for caches Key: IGNITE-4344 URL: https://issues.apache.org/jira/browse/IGNITE-4344 Project: Ignite

Re: SQL query CPU utilization too low.

Cool! I'll take a look today. Sergi 2016-11-30 18:23 GMT+03:00 Andrey Mashenkov : > Serj, you can see a PR attached to jira issue [1], that can be opened with > upsource [2]. > > Tanks, I remember about distributed queries and wiil rework them right > after we come

Re: SQL query CPU utilization too low.

Serj, you can see a PR attached to jira issue [1], that can be opened with upsource [2]. Tanks, I remember about distributed queries and wiil rework them right after we come to agreemant that the solution for simple queries is ok. [1] https://issues.apache.org/jira/browse/IGNITE-4106 [2]

[jira] [Created] (IGNITE-4343) Check mutable entries for existence properly inside DML entry processors

Alexander Paschenko created IGNITE-4343: --- Summary: Check mutable entries for existence properly inside DML entry processors Key: IGNITE-4343 URL: https://issues.apache.org/jira/browse/IGNITE-4343

[GitHub] ignite pull request #1303: IGNITE-4340 Convert results of sub SELECTs to exp...

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/1303 IGNITE-4340 Convert results of sub SELECTs to expected column types You can merge this pull request into a Git repository by running: $ git pull

Re: SQL: Table aliases not supported for SqlQuery

I don't mind to have an alias in SqlQuery, but it is better to add setter method setAlias instead of having an additional constructor with signature (String,String,String). Sergi 2016-11-30 17:55 GMT+03:00 Andrey Mashenkov : > Hi Igniters, > > H2Indexing.generateQuery()

SQL: Table aliases not supported for SqlQuery

Hi Igniters, H2Indexing.generateQuery() generates wrong sql query. It is used in SqlQuery class for queries like this: new SqlQuery(Person.class. "from Person p where p.salary > ? and p.salary <= ?") This query produce next sql query string: "SELECT "".Person._key, ""Person"._val FROM

[GitHub] ignite pull request #1302: Ignite 4341

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

Re: SQL query CPU utilization too low.

Per cache SQL parallelism level looks reasonable to me here. I'm not sure what do you mean about "prepared statement cache is useless with splitted indices", most probably you parallelize queries in some wrong way if this is true. Also do not forget about distributed joins: with parallel queries

[jira] [Created] (IGNITE-4342) DML: clear() on atomic cache causes the exception from previous failed DML statement

Sergey Kozlov created IGNITE-4342: - Summary: DML: clear() on atomic cache causes the exception from previous failed DML statement Key: IGNITE-4342 URL: https://issues.apache.org/jira/browse/IGNITE-4342

Re: SQL query CPU utilization too low.

It looks like we can't just split sql query to several threads due to H2 limitations. We can bound query thread with certain set of partitions, but, actually, H2 will read whole index and then filter entries regarding its partition. So, we can get significant speed-up that way. Unfortunatelly, H2

[jira] [Created] (IGNITE-4341) Add TeraSort example as a unit test to Ignite

Ivan Veselovsky created IGNITE-4341: --- Summary: Add TeraSort example as a unit test to Ignite Key: IGNITE-4341 URL: https://issues.apache.org/jira/browse/IGNITE-4341 Project: Ignite Issue

[jira] [Created] (IGNITE-4340) Implicitly cast new column values to expected types on SQL UPDATE

Alexander Paschenko created IGNITE-4340: --- Summary: Implicitly cast new column values to expected types on SQL UPDATE Key: IGNITE-4340 URL: https://issues.apache.org/jira/browse/IGNITE-4340

[jira] [Created] (IGNITE-4339) .NET: Execute .NET code on Java-only nodes

Pavel Tupitsyn created IGNITE-4339: -- Summary: .NET: Execute .NET code on Java-only nodes Key: IGNITE-4339 URL: https://issues.apache.org/jira/browse/IGNITE-4339 Project: Ignite Issue Type:

[GitHub] ignite pull request #1301: IGNITE-3964: SQL: implement support for table ali...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1301 IGNITE-3964: SQL: implement support for table alias Custom table name can be set for QueryEntity. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1300: Ignite 4223

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

[jira] [Created] (IGNITE-4338) Cross-schema SQL SELECT on partitioned cache fails for no good reason

Alexander Paschenko created IGNITE-4338: --- Summary: Cross-schema SQL SELECT on partitioned cache fails for no good reason Key: IGNITE-4338 URL: https://issues.apache.org/jira/browse/IGNITE-4338

[jira] [Created] (IGNITE-4337) Introduce persistence interface to allow build reliable persistence plugins

Alexey Goncharuk created IGNITE-4337: Summary: Introduce persistence interface to allow build reliable persistence plugins Key: IGNITE-4337 URL: https://issues.apache.org/jira/browse/IGNITE-4337

[jira] [Created] (IGNITE-4336) Manual rebalance can't be requested twice

Dmitriy Setrakyan created IGNITE-4336: - Summary: Manual rebalance can't be requested twice Key: IGNITE-4336 URL: https://issues.apache.org/jira/browse/IGNITE-4336 Project: Ignite Issue

[jira] [Created] (IGNITE-4335) Implement cluster ACTIVE/INACTIVE state

Alexey Goncharuk created IGNITE-4335: Summary: Implement cluster ACTIVE/INACTIVE state Key: IGNITE-4335 URL: https://issues.apache.org/jira/browse/IGNITE-4335 Project: Ignite Issue Type: