Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

+1 2017-06-10 6:19 GMT+08:00 Valentin Kulichenko : > +1 > > On Fri, Jun 9, 2017 at 3:15 PM, Andrey Mashenkov < > andrey.mashen...@gmail.com > > wrote: > > > +1 > > > > 10 июня 2017 г. 0:08 пользователь "William Do" > > написал: > > > > > +1 >

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

+1 On Fri, Jun 9, 2017 at 3:15 PM, Andrey Mashenkov wrote: > +1 > > 10 июня 2017 г. 0:08 пользователь "William Do" > написал: > > > +1 > > > > On 9 June 2017 at 21:37, Dmitriy Setrakyan > wrote: > > > > > Hm... we have

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

+1 10 июня 2017 г. 0:08 пользователь "William Do" написал: > +1 > > On 9 June 2017 at 21:37, Dmitriy Setrakyan wrote: > > > Hm... we have only 3 community members who are interested so far. Anyone > > else who may be willing to attend? > > > > On

Re: Configuration issues with IGFS in Ignite 1.9

Sorry, please disregard the last one - that's my omission. service.sh script is still fine! -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

Hm... we have only 3 community members who are interested so far. Anyone else who may be willing to attend? On Fri, Jun 9, 2017 at 12:03 AM, Sergi Vladykin wrote: > +1 > > Sergi > > 2017-06-08 23:03 GMT+03:00 Dmitriy Setrakyan : > > > +1 (I will

Re: Configuration issues with IGFS in Ignite 1.9

Vladimir, one more issue - it seems that ignite script (bin/ignite.sh) doesn't respond to 'stop' command anymore as it was the case in the earlier versions of it. As the result, linux init scripts have no control over it rather than simply kill the process. Is it the intention or am I missing

[jira] [Created] (IGNITE-5467) Exception in communication SPI can stall the cluster

Valentin Kulichenko created IGNITE-5467: --- Summary: Exception in communication SPI can stall the cluster Key: IGNITE-5467 URL: https://issues.apache.org/jira/browse/IGNITE-5467 Project: Ignite

Re: Configuration issues with IGFS in Ignite 1.9

Yey! That did the trick, thank you for your help! It'd be great to have this fix for sure! -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views

[jira] [Created] (IGNITE-5466) Web Console: New Configuration Screen

Vica Abramova created IGNITE-5466: - Summary: Web Console: New Configuration Screen Key: IGNITE-5466 URL: https://issues.apache.org/jira/browse/IGNITE-5466 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #2108: IGNITE-5455 .NET: Fix binary hash code calculatio...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2108 --- 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-5465) CREATE TABLE: add multithreaded tests

Vladimir Ozerov created IGNITE-5465: --- Summary: CREATE TABLE: add multithreaded tests Key: IGNITE-5465 URL: https://issues.apache.org/jira/browse/IGNITE-5465 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5464) DML: Can not insert arrays

Pavel Tupitsyn created IGNITE-5464: -- Summary: DML: Can not insert arrays Key: IGNITE-5464 URL: https://issues.apache.org/jira/browse/IGNITE-5464 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5463) Weird CPU load reported

Yakov Zhdanov created IGNITE-5463: - Summary: Weird CPU load reported Key: IGNITE-5463 URL: https://issues.apache.org/jira/browse/IGNITE-5463 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5462) JDBC thin driver: add complex DDL+DML test.

Taras Ledkov created IGNITE-5462: Summary: JDBC thin driver: add complex DDL+DML test. Key: IGNITE-5462 URL: https://issues.apache.org/jira/browse/IGNITE-5462 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5461) Visor show wrong statistics for off heap memory

Mikhail Cherkasov created IGNITE-5461: - Summary: Visor show wrong statistics for off heap memory Key: IGNITE-5461 URL: https://issues.apache.org/jira/browse/IGNITE-5461 Project: Ignite

Re: Configuration issues with IGFS in Ignite 1.9

Cos, This is a problem with our URI parsing. Please add a slash to the end and it should work: "hdfs://0f6e4ed13002.bigtop.apache.org:8020*/*". I'll create a ticket for this. On Thu, Jun 8, 2017 at 9:28 PM, Konstantin Boudnik wrote: > Thank you for your help, Vladimir.

[GitHub] ignite pull request #2115: IGNITE-5204: Fixed NPE on certain data with index...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/2115 IGNITE-5204: Fixed NPE on certain data with index inlining You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2114: IGNITE-5449

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

[GitHub] ignite pull request #2103: IGNITE-5431 Better handling of cache SQL flag inc...

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

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

[jira] [Created] (IGNITE-5460) Web Console: add cache group

Alexey Kuznetsov created IGNITE-5460: Summary: Web Console: add cache group Key: IGNITE-5460 URL: https://issues.apache.org/jira/browse/IGNITE-5460 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #2112: IGNITE-5339: JDBC thin driver: validate complianc...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2112 IGNITE-5339: JDBC thin driver: validate compliance You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5339

[GitHub] ignite pull request #2109: IGNITE-4431: Include date into the default format...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2109 --- 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: Data compression in Ignite 2.0

Hi * "Per-field compression" is applicable for huge BLOB fields and will impose the restrictions like unable ot index such fields, slower getting data, potential OOM issues if compression ration is too high. But for some cases it makes sense On Fri, Jun 9, 2017 at 11:11 AM, Антон Чураев

Re: Data compression in Ignite 2.0

Hi * "Per-field compression" is applicable for huge BLOB fields and will impose the restrictions like unable ot index such fields, slower getting data, potential OOM issues if compression ration is too high. But for some cases it makes sense On Fri, Jun 9, 2017 at 11:11 AM, Антон Чураев

Re: Data compression in Ignite 2.0

+1 to Vladimir. Fields encryption is a user responsibility. I see no reason to introduce additional complexity to Ignite. Sergi 2017-06-09 11:11 GMT+03:00 Антон Чураев : > Seems that Dmitry is referring to transparent data encryption. It is used > throughout the whale

Re: Data compression in Ignite 2.0

Seems that Dmitry is referring to transparent data encryption. It is used throughout the whale database industry. 2017-06-09 10:50 GMT+03:00 Vladimir Ozerov : > Dima, > > Encryption of certain fields is as bad as compression. First, it is a huge > change, which makes

Re: Data compression in Ignite 2.0

Vladimir, >> Nobody in a sane mind will >> store passwords in plain form. Instead, user should encrypt it on his own, >> choosing proper encryption parameters - algorithms, key lengths, salts, etc.. Sounds reasonable to me. But if someone want to have this feature OOTB we can continue

Re: Data compression in Ignite 2.0

Dima, Encryption of certain fields is as bad as compression. First, it is a huge change, which makes already complex binary protocol even more complex. Second, it have to be ported to CPP, .NET platforms, as well as to JDBC and ODBC. Last, but the most important - this is not our headache to

[jira] [Created] (IGNITE-5459) Deprecate IgniteConfiguration.marshaller property

Vladimir Ozerov created IGNITE-5459: --- Summary: Deprecate IgniteConfiguration.marshaller property Key: IGNITE-5459 URL: https://issues.apache.org/jira/browse/IGNITE-5459 Project: Ignite

[jira] [Created] (IGNITE-5458) Add CacheKeyConfiguration to CacheConfiguration

Vladimir Ozerov created IGNITE-5458: --- Summary: Add CacheKeyConfiguration to CacheConfiguration Key: IGNITE-5458 URL: https://issues.apache.org/jira/browse/IGNITE-5458 Project: Ignite Issue

Re: Deprecate IgniteConfiguration.marshaller and make it no-op!

Igniters, SQL do work without BinaryMarshaller. And I was wrong about DML - it appears to work as well. Let's just deprecate this. On Fri, Jun 9, 2017 at 9:55 AM, Semyon Boikov wrote: > As far as I know before 2.0 SQL worked without BinaryMarshaller, is this > support was

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

+1 Sergi 2017-06-08 23:03 GMT+03:00 Dmitriy Setrakyan : > +1 (I will attend) > > On Thu, Jun 8, 2017 at 1:02 PM, Konstantin Boudnik wrote: > > > That'd be great! Thank you! > > -- > > Take care, > > Konstantin (Cos) Boudnik > > 2CAC 8312 4870 D885 8616

Re: Deprecate IgniteConfiguration.marshaller and make it no-op!

As far as I know before 2.0 SQL worked without BinaryMarshaller, is this support was removed intentionally? Also I think it is possible to implement DML without BinaryMashaller as well? I'm not against Vladimir's suggestion, but I think it make sense to ask on user list to know if somebody uses

Re: Data compression in Ignite 2.0

>> which is much less useful. I note, in some cases there is profit more than twice per size of an object. >> Would it be possible to change your implementation to handle the encryption instead? Yes, of cource, there's not much difference between compression and encryption, including in my