[GitHub] ignite pull request #3701: IGNITE-8052: Clear error message when using a non...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/3701 IGNITE-8052: Clear error message when using a non-existing column nam… …e for CREATE TABLE primary key. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8052) Clear error message when using a non-existing column name for CREATE TABLE primary key

Roman Shtykh created IGNITE-8052: Summary: Clear error message when using a non-existing column name for CREATE TABLE primary key Key: IGNITE-8052 URL: https://issues.apache.org/jira/browse/IGNITE-8052

Re: What's about releasing Ignite 2.5 a bit earlier?

Good, hope that everyone interested has enough time to share an opinion. As a summary of this discussion, the community decided to release Ignite 2.5 on April 30. Most of the changes and features are already in the master. Who is ready to become a release manager of 2.5? We need to prepare a

Re: Optimize GridLongList serialization

Thanks, Alex. GridGain automatically compresses all the internal types. Somehow it looks like the GridLongList may have been mixed. Can you please file a ticket for 2.5 release? D. On Mon, Mar 26, 2018 at 4:55 AM, Александр Меньшиков wrote: > I investigated network

Re: Data compression design proposal

AG, I would also ask about the compression itself. How and where do we store the compression meta information? We cannot be compressing every page separately, it will not be effective. However, if we try to store the compression metadata, how do we make other nodes aware of it? Has this been

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

Taras, Please document the authentication part on a 2.5 version of the binary protocol page on readme.io. We need to share it with the guys who are developing Node.JS client right now. -- Denis On Mon, Mar 26, 2018 at 2:55 AM, Taras Ledkov wrote: > I had implement user

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

Ivan, It's all good then :) Thanks! -Val On Mon, Mar 26, 2018 at 1:50 AM, Ivan Rakov wrote: > Val, > > There's no any sense to use WalMode.NONE in production environment, it's > kept for testing and debugging purposes (including possible user activities > like capacity

Re: Different behavior when saving date from Dataframe API and RDD API

Hell, ray. > Please advise is this behavior expected? I think this behavior is expected. Because it's more efficient to query specific affinity key value. Anyway, I'm not an expert in SQL engine, so I send your question to the dev-list. Igniters, I think this user question is related to the

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hi! > As far as I remember to be PCI-DSS compliant it is sufficient to use > encryption at file system level. But it needs to be double-checked. It > requires encrypt transmission of cardholder data across open, public > networks. Could you point me where does it require DB data to be encrypted?

Re: Rebalancing - how to make it faster

>> It is impossible to disable WAL only for certain partitions without >> completely overhauling design of Ignite storage mechanism. Right now we can >> afford only to change WAL mode per cache group. Cache group rebalancing is a one cache rebalancing, and then this cache ("cache group") can be

Re: Transparent Data Encryption (TDE) in Apache Ignite

Folks, I've checked presentation. 1) It's a bad idea to allow automatic node join (sending decripted cache's keys on join). Each node join should be allowed by administrator. We have to use two-step verification in that case. - admitistrator set keystore password for each node - another

Re: Data compression design proposal

Vova, thanks for comments. Anyway, page compression at rebalancing is a good idea even is we have problems with storing on disc. 2018-03-26 19:51 GMT+03:00 Vyacheslav Daradur : > Since PDS is strongly depending on memory page's size I'd like to > compress serialized data

Re: Data compression design proposal

Since PDS is strongly depending on memory page's size I'd like to compress serialized data inside page exclude page header. On Mon, Mar 26, 2018 at 7:49 PM, Vladimir Ozerov wrote: > Alex, > > In fact there are many approaches to this. Some vendors decided stick to > page -

Re: Data compression design proposal

Alex, In fact there are many approaches to this. Some vendors decided stick to page - page is filled with data and then compressed when certain threshold is reached (e.g. page is full or filled up to X%). Another approach is to store data in memory in *larger blocks* than on the disk, and when it

Re: Data compression design proposal

Hi Anton, Do you have suggestions for this approach? Sincerely, Dmitriy Pavlov пн, 26 мар. 2018 г. в 19:46, Anton Vinogradov : > Can we use another approach to store compressed pages? > > 2018-03-26 19:06 GMT+03:00 Dmitry Pavlov : > > > +1 to Alexey's

Re: Data compression design proposal

Can we use another approach to store compressed pages? 2018-03-26 19:06 GMT+03:00 Dmitry Pavlov : > +1 to Alexey's concern. No reason to compress if we use previous offset as > pageIdx*pageSize. > > пн, 26 мар. 2018 г. в 18:59, Alexey Goncharuk

[jira] [Created] (IGNITE-8051) Put operation may hang on LOCAL TRANSACTIONAL cache if it was stopped asynchronously.

Pavel Pereslegin created IGNITE-8051: Summary: Put operation may hang on LOCAL TRANSACTIONAL cache if it was stopped asynchronously. Key: IGNITE-8051 URL: https://issues.apache.org/jira/browse/IGNITE-8051

[jira] [Created] (IGNITE-8050) Throw a meaningful exception when user issues TX SQL keyword with MVCC turned off

Alexander Paschenko created IGNITE-8050: --- Summary: Throw a meaningful exception when user issues TX SQL keyword with MVCC turned off Key: IGNITE-8050 URL: https://issues.apache.org/jira/browse/IGNITE-8050

Re: Data compression design proposal

+1 to Alexey's concern. No reason to compress if we use previous offset as pageIdx*pageSize. пн, 26 мар. 2018 г. в 18:59, Alexey Goncharuk : > Guys, > > How does this fit the PageMemory concept? Currently it assumes that the > size of the page in memory and the size

Re: Data compression design proposal

Guys, How does this fit the PageMemory concept? Currently it assumes that the size of the page in memory and the size of the page on disk is the same, so only per-entry level compression within a page makes sense. If you compress a whole page, how do you calculate the page offset in the target

[jira] [Created] (IGNITE-8049) Limit the number of operation cycles in B+Tree

Alexey Goncharuk created IGNITE-8049: Summary: Limit the number of operation cycles in B+Tree Key: IGNITE-8049 URL: https://issues.apache.org/jira/browse/IGNITE-8049 Project: Ignite

[jira] [Created] (IGNITE-8048) Dynamic indexes are not stored to cache data on node join

Alexey Goncharuk created IGNITE-8048: Summary: Dynamic indexes are not stored to cache data on node join Key: IGNITE-8048 URL: https://issues.apache.org/jira/browse/IGNITE-8048 Project: Ignite

Re: Data compression design proposal

Gents, If I understood the idea correctly, the proposal is to compress pages on eviction and decompress them on read from disk. Is it correct? On Mon, Mar 26, 2018 at 5:13 PM, Anton Vinogradov wrote: > + 1 to Taras's vision. > > Compression on eviction is a good case to store

[jira] [Created] (IGNITE-8047) SQL: optimize simple COUNT with DISTINCT query.

Andrew Mashenkov created IGNITE-8047: Summary: SQL: optimize simple COUNT with DISTINCT query. Key: IGNITE-8047 URL: https://issues.apache.org/jira/browse/IGNITE-8047 Project: Ignite

[jira] [Created] (IGNITE-8046) New flaky tests added in JettyRestProcessorAuthenticationSelfTest

Dmitriy Pavlov created IGNITE-8046: -- Summary: New flaky tests added in JettyRestProcessorAuthenticationSelfTest Key: IGNITE-8046 URL: https://issues.apache.org/jira/browse/IGNITE-8046 Project:

Re: Rebalancing - how to make it faster

Dmitry, It is impossible to disable WAL only for certain partitions without completely overhauling design of Ignite storage mechanism. Right now we can afford only to change WAL mode per cache group. The idea is to disable WAL when node doesn't have any partition in OWNING state, which means it

[jira] [Created] (IGNITE-8045) Direct-IO component is not published into maven repository.

Vyacheslav Koptilin created IGNITE-8045: --- Summary: Direct-IO component is not published into maven repository. Key: IGNITE-8045 URL: https://issues.apache.org/jira/browse/IGNITE-8045 Project:

Re: Rebalancing - how to make it faster

+1 for IEP creation 2018-03-23 22:40 GMT+03:00 Dmitry Pavlov : > Denis, as I understood, there is and idea to exclude only rebalanced > partition(s) data. All other data will go to the WAL. > > Ilya, please correct me if I'm wrong. > > пт, 23 мар. 2018 г. в 22:15, Denis

[GitHub] ignite pull request #3699: IGNITE-6842: add default behavior by stopping all...

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

Re: Data compression design proposal

+ 1 to Taras's vision. Compression on eviction is a good case to store more. Pages at memory always hot a real system, so complession in memory will definetely slowdown the system, I think. Anyway, we can split issue to "on eviction compression" and to "in-memory compression". 2018-03-06 12:14

[GitHub] ignite pull request #3690: IGNITE-7928 .NET: Exception is not propagated to ...

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

[GitHub] ignite pull request #3693: IGNITE-8036 MulticastIpFinder is replaced with Vm...

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

[GitHub] ignite pull request #3700: IGNITE-6839 Ignite Compatibility: flaky test test...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/3700 IGNITE-6839 Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2 & 2_3 ….util.IgniteUtils.classLoaderUrls(Ljava/lang/ClassLoader;)[Ljava/net/URL;" was fixed; code cleanup

PR#3697 IGNITE-8021: Delete cache config files when destroyed

Hi Team, Could you review this PR https://github.com/apache/ignite/pull/3697 please? Tests result: https://ci.ignite.apache.org/viewLog.html?buildId=1159660 Jira ticket: https://issues.apache.org/jira/browse/IGNITE-8021 -- Sincerely yours, Ivan Daschinskiy

Re: IEP-14: Ignite failures handling (Discussion)

Yakov, I agree with Andrey that a separate abstraction for failure handling makes sense. First, using event listeners for this kind of response allows users to install multiple listeners, which may be invoked in an unpredictable order, this looks error-prone to me. Second, we may add an

[jira] [Created] (IGNITE-8044) IgniteQueryGenerator.getOptions() method should properly handle empty list of parameters.

Vyacheslav Koptilin created IGNITE-8044: --- Summary: IgniteQueryGenerator.getOptions() method should properly handle empty list of parameters. Key: IGNITE-8044 URL:

Optimize GridLongList serialization

I investigated network loading and found that a big part of internal data inside messages is `GridLongList`. It is a part of `GridDhtTxFinishRequest`, `GridDhtAtomicDeferredUpdateResponse`, `GridDhtAtomicUpdateRequest`, `GridNearAtomicFullUpdateRequest` and `NearCacheUpdates`. So I think it has

[jira] [Created] (IGNITE-8043) Thin client fails while connecting to Ignite instance in docker container

Jiri Tobisek created IGNITE-8043: Summary: Thin client fails while connecting to Ignite instance in docker container Key: IGNITE-8043 URL: https://issues.apache.org/jira/browse/IGNITE-8043 Project:

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

I had implement user credential store according with the previous discussion about user authentication. Now JDBC thin, and ODBC support user authentication. We haven't implemented it for all thin client because protocols are not similar. I see two ways to implement authentication for thin

[GitHub] ignite pull request #3699: IGNITE-6842: add default behavior by stopping all...

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/3699 IGNITE-6842: add default behavior by stopping all instances for tests 1. Stop all grids by default in aftreTestsStop method; 2. Throw exception in case stopping process fails; You can merge

[GitHub] ignite pull request #3665: ignite-8004 set compatibilityMode to true in coll...

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

[GitHub] ignite pull request #3698: Ignite 2.4.4 .net

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

[GitHub] ignite pull request #3671: IGNITE-7852: Supported username/password authenti...

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

[GitHub] ignite pull request #3698: Ignite 2.4.4 .net

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

[GitHub] ignite pull request #3697: IGNITE-8021 Delete cache config files when destro...

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/3697 IGNITE-8021 Delete cache config files when destroyed You can merge this pull request into a Git repository by running: $ git pull https://github.com/ivandasch/ignite ignite-8021

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

Val, There's no any sense to use WalMode.NONE in production environment, it's kept for testing and debugging purposes (including possible user activities like capacity planning). We already print a warning at node start in case WalMode.NONE is set: U.quietAndWarn(log,"Started write-ahead log

[jira] [Created] (IGNITE-8042) .NET thin client: Add username/password to handshake

Vladimir Ozerov created IGNITE-8042: --- Summary: .NET thin client: Add username/password to handshake Key: IGNITE-8042 URL: https://issues.apache.org/jira/browse/IGNITE-8042 Project: Ignite

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

Taras, Could you please chime in? On Mon, Mar 26, 2018 at 9:56 AM, Pavel Tupitsyn wrote: > I've started this task, and the property name combined with lack of > javadoc seems confusing and misleading: > > * Turns out this authentication is only for thin clients > * Not

[GitHub] ignite pull request #3696: IGNITE-8034 .NET: Add IgniteConfiguration.Authent...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3696 IGNITE-8034 .NET: Add IgniteConfiguration.AuthenticationEnabled You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-8034

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

I've started this task, and the property name combined with lack of javadoc seems confusing and misleading: * Turns out this authentication is only for thin clients * Not clear how to configure and use it, even after digging through Jira and devlist How do I write test to ensure it works?