Re: Default failure handler was changed for tests

never coders. > > Please see https://discourse.pi-hole.net/faq - has absolutely nothing in > common with Apache Guides, but says the same things. It is a practical > necessity to maintain a friendly atmosphere. > > чт, 6 дек. 2018 г. в 10:31, Nikolay Izhikov : > > > I

Re: Default failure handler was changed for tests

o improve the > patch then let's do it. > чт, 6 дек. 2018 г. в 10:41, Nikolay Izhikov : > > > > Dmitriy Ryabov, Dmitriy Pavlov, sorry. > > > > Of course it should be "NOT to blame author". > > > > Sorry, one more time. > > > > чт, 6

Re: [ANNOUNCE] Apache Ignite 2.7.0 Released

Dmitriy. Yes, we should. Please, tell me mail of this channel. чт, 6 дек. 2018 г., 14:13 Dmitriy Pavlov dpav...@apache.org: > Nikolay, thank you for your efforts! > > Should we announce a release in a special Apache-wide channel? > > чт, 6 дек. 2018 г. в 10:36, Nikolay Izhi

Re: [ANNOUNCE] Apache Ignite 2.7.0 Released

gt; > чт, 6 дек. 2018 г. в 14:30, Nikolay Izhikov : > > > Dmitriy. > > > > Yes, we should. Please, tell me mail of this channel. > > > > чт, 6 дек. 2018 г., 14:13 Dmitriy Pavlov dpav...@apache.org: > > > > > Nikolay, thank you for your efforts! &

Re: Default failure handler was changed for tests

ate stable workarounds, which will never be fixed. >>>>>> >>>>>> I agree with Nikolay's solution. If no one minds, I'll create >> ticket >>>> for >>>>>> appropriate changes and recheck issues. >>>>>> >>>

Re: [ANNOUNCE] Apache Ignite 2.7.0 Released

here is a WebConsole > > related bullet point. > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > > > > Prachi, please release the new website pages. > > > > Dmitriy P, there were some security related changes. Please go ahead and > > un

Re: [ANNOUNCE] Apache Ignite 2.7.0 Released

luence/display/IGNITE/Release+Process > > Prachi, please release the new website pages. > > Dmitriy P, there were some security related changes. Please go ahead and > uncover them. > > -- > Denis > > On Thu, Dec 6, 2018 at 4:02 AM Nikolay Izhikov wrote: > > &

Re: [RESULT] [VOTE] Apache Ignite 2.7.0 Release (RC2)

i Garg > wrote: > > Hello Igniters, > > The documentation for Apache Ignite 2.7.0 is now public on readme.io > <https://apacheignite.readme.io/docs/>. > > -Prachi > > On Wed, Dec 5, 2018 at 9:35 AM Nikolay Izhikov wrote: > > > Yes, Denis. > >

Re: Clean up of our PRs and IEPs before 2019

Hello, Dmitriy. What, exactly concerns newcomers? What is wrong with opened PR? How project will benefit from closed PR? > The same proposal is related to IEP statuses. If you were involved in an IEP, please validate its status +1. We should maintain IEP description up to date. пн, 10 дек. 2018

Re: Schema in CacheConfig is not updated after DDL commands(Add/drop column, Create/drop index)

Vladimir. Since we are talking about internal component(Spark Data Frame integration) can we use same technique as JdbcRequestHandler to obtain columns metadata? Seems, code above will fetch up to date columns info: org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler#getColumnsMeta

Re: Clean up of our PRs and IEPs before 2019

to PRs). > > > > > > Another benefit of revising this list, if there are any changes which > > > were not accomplished with a proper ticket with PA status, we will > > > > identify > > > a number of additional contributions to be applied to the codeb

Re: Pre-touch for Ignite off-heap memory

Hello, Stanislav. As far as I can see, we have controversal ticket based on previous dev-list discussion: IGNITE-9113 - Allocate memory for a data region when first cache assigned to this region is created [1] I planned to implement it soon. Looks like we should have several options of memory(

Re: newbie to Apache Ignite.

Hello, Lawrence. Can you share code to reproduce the issue? чт, 13 дек. 2018 г., 0:15 lawrence@barclays.com.invalid: > Hi, > >I just started looking to adapt Apache Ignite into our project as an > in-memory distributed cache and potentially as distributed computing grid. > >An Ignit

Re: Service grid redesign

Hello, Denis. Great news. > *1. Testing of the cache-based implementation of the service grid.* > I think, we should make a test suite, that will test the old implementation> > until we> remove it from the project. Aggree. Let's do it. > *2. DynamicServiceChangeRequest.* > I think, this class

Re: Pre-touch for Ignite off-heap memory

if you believe that pre-touch > will help product users then I have nothing against it. > ср, 12 дек. 2018 г. в 11:09, Nikolay Izhikov : > > > > Hello, Stanislav. > > > > As far as I can see, we have controversal ticket based on previous > dev-list discussion: >

Re: Critical worker threads liveness checking drawbacks

gt; > [2] https://github.com/apache/ignite/pull/4862 > >> > > >> > On Fri, 28 Sep 2018 at 16:58 Yakov Zhdanov > wrote: > >> > > >> > > Config option + mbean access. Does that make sense? > >> > > > >> > &

Re: Service grid redesign

t; -> "Deployment" > > > Personally, I agree with Nikolay, because it's more descriptive since > > > manages several services, not single. > > > But, I understand Denis's point of view, we have a lot of classes with > > > "Service" prefix in naming a

Re: Service grid redesign

t; the event object. > But this solution is the same, it's just a matter of taste. > > If anybody wants to look the the code of the PR, please consider these > points as well. > > Denis > > ср, 19 дек. 2018 г. в 17:37, Nikolay Izhikov : > > > Denis, > &g

Re: Service grid redesign

de style. > > > > > > Stan > > > > > > From: Vyacheslav Daradur > > > Sent: 21 декабря 2018 г. 14:58 > > > To: dev@ignite.apache.org > > > Subject: Re: Service grid redesign > > > > > > Igniters, > > > >

Re: Service grid redesign

Hello, Igniters. I've merged Service Grid Redesign - Phase 1 to the master. Vyacheslav, great contribution! Thanks for all Ignite veterans both for the code and design review. В Пн, 24/12/2018 в 20:50 +0300, Nikolay Izhikov пишет: > Hello, Igniters. > > Please, let us know, if s

System Worker Failure Handler on local laptop

Hello, Igniters. I run into issue with critical system worker failure handler. I just run `IgniteDataFrameSuite` and it terminates on random test. My laptop doesn't have bleeding edge hardware, so tests can take significant amount of time. Looks like our watch dog too aggressive on development env

Re: System Worker Failure Handler on local laptop

sue, you should set > DataStorageConfiguration#setCheckpointReadLockTimeout to 0. > > Should we somehow announce it on the user-list or highlight on readme.io? > > чт, 27 дек. 2018 г. в 11:57, Nikolay Izhikov : > > > Hello, Igniters. > > > > I run into issue with

Re: Make Teamcity Green Again

+1 to Dmitry Pavlov from me. Green team city would be very helpful. > If you are a newcomer, please share your feeling: are you confused by test > failures on Teamcity? I'm working on my very first ignite issue and it's not easy to understand TC build results. 21.07.2017 00:30, Dmitriy Set

Re: .Net client call tx,close in other thread

heAbstractTransactionalTest.TestTxStateAndExceptions -- Nikolay Izhikov nizhikov@gmail.com -- Nikolay Izhikov nizhikov@gmail.com

ContinuousQueryWithTransformer implementation questions - 2

Hello, Igniters. I'm working on IGNITE-425 [1] issue. Text of issue: === Currently if updated entry passes the filter, it is sent to node initiated the query entirely. It would be good to provide user with the ability to transform entry and, for example, select only fields that are important

Re: ContinuousQueryWithTransformer implementation questions - 2

Hi, Yakov. If filter throws exception entry would be passed to listener. > Nikolay, I would also suggest you extract some super class for continuous > query. It will help to avoid code duplicates. Yes, I will do this after reaching consensus on API changes. 29.08.2017 14:04, Yakov Zhdanov пише

Re: ContinuousQueryWithTransformer implementation questions - 2

Yakov. I think exception equals `true` is intended behavior. Filter evaluation implementation from master - [1] Test from master to check filter exception(without explicit asserts checking listeners call) - [2] Here is my quick test with asserts on listener call after filter exception: ``` p

Re: ContinuousQueryWithTransformer implementation questions - 2

Yakov Zhdanov пишет: Igniters, Does anyone else see potential issues on user side with current approach? Sam, is this JCache requirement? --Yakov 2017-08-29 15:16 GMT+03:00 Nikolay Izhikov : Yakov. I think exception equals `true` is intended behavior. Filter evaluation implementation from master

Re: ContinuousQueryWithTransformer implementation questions - 2

ent behavior is required by jcache, but now I can not find anything about this neither in spec nor in jcache tck tests. So I think we can change current behavior. Thanks On Tue, Aug 29, 2017 at 9:48 PM, Nikolay Izhikov wrote: Yakov. I found following description in jcache javadoc [1] - === Re

Re: ContinuousQueryWithTransformer implementation questions - 2

Hello, Yakov. The new class is OK - got it. Thanks! > Should we extract a super class? Yes, we should. I already have done it. See my last commit in PR - https://github.com/apache/ignite/pull/2372/commits/af1ed2e4dbef4ba5999f8566198cb75ad922f93b > We can put hard requirement that filter and

Re: Monitoring of active transactions

Hello, Ilya. Great! Thanks! Can I extend your idea a bit? I think it be very useful monitor all-user provided listeners and callbacks also. To handle following scenarios: 1а. User starts a job with ExecutorService, IgniteCompute or similar. 1b. User creates ContinuousQuery with remoteFilter

Re: ContinuousQueryWithTransformer implementation questions - 2

> > it >> > > also has a rmtFilter, which will also be called on event nodes. Will >> the >> > > onEvent() then invoked on the listener anyway, regardless of the >> filter >> > > result?

Re: Ignite Benchmarking Rules

Hello, Dmitriy. I think experienced members of community have specific number for benchmarking. Can we start from reference hardware configuration: Num of CPU, RAM and HDD(SDD?) configuration, network configs, etc. Can someone share that kind of knowledge - Which hardware is best for Ignit

Re: Binary compatibility of persistent storage

Hello, Vladimir. I prefer 2 option. > 2) No compatibility, but provide migration instruments I think we have to provide some tool for converting WAL files from any older format to current. 19.09.2017 14:16, Vladimir Ozerov пишет: igniters, Ignite doesn't have compatibility for binary proto

Re: Spark+Ignite SQL syntax proposal

Hello, Ray. I think it can be done as a second step. After DataFrame for a current Spark release would be merged. Thoughts? 07.10.2017 16:42, Ray пишет: Hi Nikolay, Could you also implement the DataFrame support for spark-2.10 module? There's some legacy spark users still using Spark 1.6, the

Re: Transparent Data Encryption (TDE) in Apache Ignite

in scope of page. Continious IV accumulating CBC mode for > whole store seems to be not working. Same question about IV is applicable > to WAL records. > > Could we consider ECB? or limit CBC with zero or well known IV? > > Sincerely, > Dmitriy Pavlov > > сб, 5 мая 2

Re: Transparent Data Encryption (TDE) in Apache Ignite

implementation, but will allow us to move by small > steps, it also allows us to merge smaller changes to master. > > Sincerely, > Dmitriy Pavlov > > пн, 14 мая 2018 г. в 16:53, Nikolay Izhikov : > > > Hello, guys. > > > > We had private discussio

Re: stopAllGrids() used by default and further steps

Yes. В Пн, 14/05/2018 в 20:48 +0300, Dmitry Pavlov пишет: > Hi Nikolay, > > Would you have a minute to finalize this review? > > Sincerely, > Dmitriy Pavlov > > пт, 4 мая 2018 г. в 16:05, Maxim Muzafarov : > > Dmitry, > > > > Task of migration to JUnit 4/5 sounds very interesting for me, but I

Re: What's new for thin client protocol v1.1.0 vs v1.0.0

Hello, Igniters. AFAIK, we have backward compatibility for a thin client protocol. But, currently, we doesn't have any kind of tests to check it. Do we have a ticket to create backward compatibility tests? В Пн, 04/06/2018 в 13:30 +0300, Igor Sapego пишет: > Hi Aleksandr, > > There are no cha

Re: Upgrading Ignite to JCache 1.1

Hello, Igniters. Actually, I don't understand why we should merge in master something broken. Currently, Ignite is not ready for JCache 1.1. Only change I see in PR is new profile [1]. Is it required to have it to continue jcache 1.1 support implementation? I think Alexandex can proceed with cur

Re: Upgrading Ignite to JCache 1.1

Vyacheslav, Let's create build plan on TC for this profile. Why we need to merge it in master now? В Вт, 05/06/2018 в 13:29 +0300, Vyacheslav Daradur пишет: > Nikolay, there isn't anything broken in PR. > > The PR is needed to add new build-plan on TC. > > We need tools to check that fixes for

Re: Upgrading Ignite to JCache 1.1

; > On Tue, Jun 5, 2018 at 1:31 PM, Nikolay Izhikov wrote: > > Vyacheslav, > > > > Let's create build plan on TC for this profile. > > Why we need to merge it in master now? > > > > В Вт, 05/06/2018 в 13:29 +0300, Vyacheslav Daradur пишет: > >

Re: Upgrading Ignite to JCache 1.1

Alex, please try to run this build plan for your branch https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11 В Вт, 05/06/2018 в 13:56 +0300, Nikolay Izhikov пишет: > Guys, we had a private talk with Vyacheslav and Dmitriy Pavlov. > Here are its resulst: >

Re: Thin clients compatibility policy

+1 From me. As I wrote in previous mail-threads, I think we need to create test framework to be able to test compatibility for all clients we have. AFAIK, currently, there is no possibility to automatically check compatibility. В Ср, 06/06/2018 в 11:39 +0300, Vladimir Ozerov пишет: > Igniters,

Re: errors during ignite mvn compilation with skipTest=false

Hello, vbm. You should add "-DskipTests". Please, check out [1]. mvn clean install -Pall-java,all-scala,licenses *-DskipTests* [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ProjectBuild В Ср, 06/06/2018 в 09:47 -0700, vbm пишет: > Hi, > > When I tr

IEP-18 TDE: Prototype

Hello, guys. I've implement prototype of TDE implementation [1] Vladimir, can you do some prereview of this prototype? Any feedback on public API or any other part of implementation are welcome. I have several questions I want to discuss. 1. Right place for a cache(data) key: Currently,

Re: Ignite 2.6 emergency release suggestion

Hello, guys. I try my best to do review in a next few days. В Вт, 12/06/2018 в 11:28 -0700, Denis Magda пишет: > Agree with Ray. The ticket has been already reviewed and requires us to run > tests for an isolated module - Spark. > > Dmitriy Pavlov, Nickolay Izhikov, could you step in as final r

Re: Entries are not loaded into cache during cache store loading

Hello, Aleksey. By "cache store" you mean 3-d party cache store [1] ? https://apacheignite.readme.io/docs/3rd-party-store В Вт, 19/06/2018 в 13:10 +0300, Aleksey Kuznetsov пишет: > Hi, Igniters! > > During test bug fixing [1], I stumbled on the following issue: > When we perform cache store loa

Re: IEP-22: Direct Data Load proposal

Hello, Vladimir. Does this IEP fit with IEP-18: TDE? Do we allow to user to load data into encrypted cache? В Ср, 20/06/2018 в 18:08 +0300, Vladimir Ozerov пишет: > Igniters, > > Initial data load is one of the most important use cases for our product. > This is one the first things user try to

Re: JCache 1.1: IGNITE-8715 Problems with Closeable objects from Factory

Hello, Alex. Issue looks trivial from your description. Can you clarify - What is the issues with obvious decision you describe? В Чт, 21/06/2018 в 17:48 +0300, Александр Меньшиков пишет: > Hi, Igniters! > Can someone give me advice about IGNITE-8715 [1]? > It's a part of IEP-21 [2] about updatin

TDE: Upgrade Team City JDK

Hello, Igniters. I'm trying to run tests for TDE branch. It seems I'm facing with known JDK bug [1] Here is log from Team City [2]. As I can see current Team City jdk is 1.8.0_77-b03 Issue JDK-8149411 fixed in 8u102. Can we upgrade JDK on Team City? [1] https://bugs.openjdk.java.net/browse/JDK

Re: TDE: Upgrade Team City JDK

a later. > > > > > On 25 Jun 2018, at 10:33, Nikolay Izhikov wrote: > > > > Hello, Igniters. > > > > I'm trying to run tests for TDE branch. > > > > It seems I'm facing with known JDK bug [1] > > Here is log from Team Cit

Re: TDE: Upgrade Team City JDK

p;_focus=30899 В Пн, 25/06/2018 в 13:24 +0300, Petr Ivanov пишет: > I’ve modified filter requirements for JDK for Spring build configuration to > run only on u151/u171 of JDK-1.8.0 (it will be 55 agent). > Hope this will be enough. > > > > > On 25 Jun 2018, at 12:54

TeamCity. Spark Data Frame. RDD suite should be reconfigured

Hello, Igniters. I found that RDD suite doesn't run all scala tests and should be reconfigured. 1. Parameter. TEST_SUITE = "IgniteRDDTestSuite,IgniteDataFrameSuite" 2. Buil Steps. Step3. Additional Maven command line parameters: "-Pall-java,scala,scala-test". Petr, can you edit this settings? S

Re: TeamCity. Spark Data Frame. RDD suite should be reconfigured

FrameIgniteSessionWriteSpec,IgniteSQLDataFrameSpec,IgniteSQLDataFrameWriteSpec’ > — both ‘IgniteRDDTestSuite' and ‘IgniteDataFrameSuite’ are present. > 2. Step3 Maven task had ‘-Pall-java,scala-2.10,tensorflow’ — should I add > ’scala’ and 'scala-test’ profiles as well? > &g

Re: TeamCity. Spark Data Frame. RDD suite should be reconfigured

Please, remove `scala-2.10` from profiles, also. В Вт, 26/06/2018 в 14:39 +0300, Petr Ivanov пишет: > I’ve modified list of suites and added ‘scala’ and ’scala-test’ to profiles > list. > Please check build. > > > > > On 26 Jun 2018, at 14:28, Nikolay Izhikov wrote: &

Re: TeamCity. Spark Data Frame. RDD suite should be reconfigured

For `RDD` suite, we need use `test` goal instead of `surefire:test`, also. Because, scala tests runs with org.scalatest:scalatest-maven-plugin:2.0.0 В Вт, 26/06/2018 в 14:53 +0300, Nikolay Izhikov пишет: > Please, remove `scala-2.10` from profiles, also. > > В Вт, 26/06/2018 в 14

Re: TDE: Upgrade Team City JDK

Petr, can you make suggested jdk upgrade? В Пн, 25/06/2018 в 14:28 +0300, Nikolay Izhikov пишет: > Petr. > > One more thing: > > We need to install "Java Cryptography Extension (JCE) Unlimited Strength > Jurisdiction Policy Files" [1] to enable usage of JDK pr

Re: Ignite 2.6 emergency release suggestion

Hello, Igniters. We have private discussion with Vladimir Ozerov and Dmitry Pavlov. IGNITE-6055 has to be included in 2.6, also. Final review from Vladimir required to merge this ticket. Do we have a chance to include this ticket to 2.6? В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет: > Hi

Re: Ignite 2.6 emergency release suggestion

Also, Igniters, be aware https://issues.apache.org/jira/browse/IGNITE-8534 merged to master and cherry picked to 2.6 branch. В Вт, 26/06/2018 в 19:29 +0300, Nikolay Izhikov пишет: > Hello, Igniters. > > We have private discussion with Vladimir Ozerov and Dmitry Pavlov. > > IGN

Re: TDE: Upgrade Team City JDK

enabled compatible agents. > Looks like it fixed the issue. > > > > > On 26 Jun 2018, at 19:27, Nikolay Izhikov wrote: > > > > Petr, can you make suggested jdk upgrade? > > > > В Пн, 25/06/2018 в 14:28 +0300, Nikolay Izhikov пишет: > > > Petr. >

Re: TDE: Upgrade Team City JDK

> > > On 27 Jun 2018, at 00:42, Nikolay Izhikov wrote: > > > > Hello, Petr. > > > > Thanks a lot! > > I see success spring encryption tests now [1] > > > > I've added encryption tests to core module also. > > Can we set same rule f

Re: Ignite 2.6 emergency release suggestion

Hello, Dmitriy. I fixed this issue, already. Please, check it. В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет: > Hi Denis, > > currently anyway we have TC issue came from spark version migrations. > > I also currently experiencing challenges with my local environment setup. > So I guess we

Re: TDE: Upgrade Team City JDK

fore restriction) to these > suites. > > On Wed, Jun 27, 2018 at 11:39 AM, Petr Ivanov wrote: > > > IgniteSpiTestSuite is called from ’SPI’ build type and I’ve added agent > > filter there. > > IgniteKernalSelfTestSuite is not found in build types. > > >

Re: TDE: Upgrade Team City JDK

7/06/2018 в 18:44 +0300, Dmitry Pavlov пишет: > Hi Nikolay, > > can we add option enables AES 128 for test mode? This should work well > without update env. > > Sincerely, > > ср, 27 июн. 2018 г. в 18:43, Petr Ivanov : > > > > > > > > On 27 Jun 2

Re: data extractor

Hello, Dmitriy. Should we support extraction of encrypted data? There will be 2 type of keys we should load to successfully extract data: * master key: keystore + password required. * cache keys: masterkey + access to metastore required. TDE task is almost done, please, take a look. ticket - h

Re: Clusterwide settings validation

Hello, Andrew. Can you clarify your question? What checks do you mean, exactly? Do you mean internal Ignite checks or user-provided checks? Ignite checks configuration consistency on node start [1]. Ignite do have consistency check for a joining node. Take a look at [2] and all of it children.

Re: RDD spark 2.10 version upgrade & TC suites

Hello, Igniters. 1. There is no spark_2.10 module in master and ignite-2.6. 2. We don't need "RDD (Spark 2.10)" build. Please, delete it from Team City. В Чт, 12/07/2018 в 23:19 +0300, Dmitry Pavlov пишет: > I guess related topic is > http://apache-ignite-developers.2346864.n4.nabble.com/Review

TC issue. Spring Data build.

Hello, Igniters. I faced with TC issue for my PR [1] Seems like some TC misconfiguration. Locally, all runs OK. AFAIK, other Igniters also gets this error on TC. Please, help me with TC configuration. https://ci.ignite.apache.org/viewLog.html?buildId=1512664&tab=buildResultsDiv&buildTypeId=Igni

Re: Desynchronization of true repo and github repo

When I'm try to push 8633d34e to master, GitHub repo doesn't contain Yury commit. It appear on GitHub only after my merge and push. пт, 20 июля 2018 г., 14:53 Dmitry Pavlov : > Hi Yury, > > it seems commit has appeared now: > > https://github.com/apache/ignite/commit/26e405281792d38b5505cde22b5c

Re: Spark DataFrame Partition Ordering Issue

Hello, Stuart. I will investigate this issue and return to you in a couple days. пт, 20 июля 2018 г., 17:59 Stuart Macdonald : > Ignite Dev Community, > > I’m working with the Ignite 2.4+ Spark SQL DataFrame functionality and > have run into what I believe to be a bug where spark partition infor

Re: Spark DataFrame Partition Ordering Issue

Hello, Stuart. I'm able to reproduce your issue So I've created the ticket for it - https://issues.apache.org/jira/browse/IGNITE-9063 Do you want to provide a fix? В Пт, 20/07/2018 в 19:37 +0300, Nikolay Izhikov пишет: > Hello, Stuart. > > I will investigate this issue and

Re: ConcurrentLinkedHashMap works incorrectly after clear()

Hello, Ilya. May be we need to proceed with ticket [1] "Get rid of org.jsr166.ConcurrentLinkedHashMap"? Especially, if this class is broken and buggy. [1] https://issues.apache.org/jira/browse/IGNITE-7516 В Вт, 24/07/2018 в 16:20 +0300, Ilya Lantukh пишет: > Thanks for revealing this issue! >

Re: Deprecating LOCAL cache

Huge +1 from me. One more SO question about LOCAL caches - https://stackoverflow.com/questions/49051079/is-it-possible-to-perform-sql-query-with-distributed-join-over-a-local-cache-and "It is not possible to perform joins (both distributed an co-located) between LOCAL and PARTITIONED caches. Th

Re: Apache Ignite 2.7: scope, time and release manager

ain. > > > > > > > > p. > > > > > > > > [1] https://jira.apache.org/jira/browse/IGNITE-7782 > > > > [2] https://jira.apache.org/jira/browse/IGNITE-7783 > > > > [3] https://jira.apache.org/jira/browse/IGNITE- > > > > > > >

Re: Spark DataFrames With Cache Key and Value Objects

Hello, Stuart. I like your idea. > 1. Ignite BinaryObjects, in which case we’d need to supply a Spark Encoder > implementation for BinaryObjects > 2. Kryo-serialised versions of the objects. Seems like first option is simple adapter. Am I right? If yes, I think it's a more efficient way compari

TDE. Phase 1 is ready for review

Hello, Igniters. TDE. Phase 1 [1] is ready for review [2]. I meet some corner cases during development I want to describe: 1. Creation of Cache Group Encryption Keys: 1.1. To build cache create request we has to create Cache Group Encryption Key. 1.2. To create Cache Group Encr

Re: Spark DataFrames With Cache Key and Value Objects

UDF so that the > user interface would be standard Spark: > > Dataset dataFrame = ... > DataSet dataSet = > dataFrame.select(“_val_).as(Encoders.kryo(MyValClass.class)) > > I’ll create a ticket and maybe put together a test case for further > discussion? > > Stuart. > &

Re: Spark DataFrames With Cache Key and Value Objects

his should be supported using IgniteRDD I believe. > > > > 2. Based on DataFrame providing a class. This would just work out of the > > > > box I guess. > > > > > > Of course, this needs to be tested and verified, and there might be > > > >

Re: Apache Ignite 2.7: scope, time and release manager

Hello, Igniters. Release page created [1]. [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7 В Пт, 27/07/2018 в 00:52 -0700, Denis Magda пишет: > Sure, it can wait. Thanks! Take a rest ) > > On Thu, Jul 26, 2018 at 11:39 PM Nikolay Izhikov > wrote: > &

Re: Apache Ignite 2.7: scope, time and release manager

his page. It seems font size for some filters is bigger than > > for others. It is intentionally done this way? > > > > Sincerely, > > Dmitriy Pavlov > > > > вт, 31 июл. 2018 г. в 15:57, Nikolay Izhikov : > > > > > Hello, Igniters. > >

Re: TDE: Upgrade Team City JDK

ug&expand=all&buildId=1566703&_focus=446976 [2] https://bugs.openjdk.java.net/browse/JDK-8149411 В Ср, 27/06/2018 в 18:50 +0300, Nikolay Izhikov пишет: > Hi. > > > can we add option enables AES 128 > > Currently, 128 bit key used [1] > > > > I guess we sh

Re: TDE: Upgrade Team City JDK

Вт, 31/07/2018 в 16:45 +0300, Petr Ivanov пишет: > No we cannot do it right now. > > What JDK is required for running this build? > I can filter agents with correct JDK for now. > > > > > On 31 Jul 2018, at 16:35, Nikolay Izhikov wrote: > > > > Hello

Re: Assign JIRA tickets to someone else

How about mention desired expert with some predefined message? So expert can setup simple email filter and know about tickets that have to be done. Example: "[~dpavlov] TFY" - ticket for you. В Вт, 31/07/2018 в 14:04 -0700, Dmitriy Setrakyan пишет: > Dmitriy, > > I would agree with everything

Re: Exchange stucks while node restoring state from WAL

Hello, Maxim. > 1) Is it correct that readMetastore() happens after node starts> but before > including node into the ring?> I think yes. You can have some kind of metainformation required on node join. > 5) Does in our final solution for new joined node readMetastore> and > restoreMemory sh

Re: IgniteSparkSession Should Copy State on cloneSession()

Hello, Stuart. Looks like a bug. Please, go ahead with fixing it. В Пт, 03/08/2018 в 12:43 +0100, Stuart Macdonald пишет: > Hello Igniters, > > The IgniteSparkSession class extends SparkSession and overrides the > cloneSession() method. The contract for cloneSession() explicitly states > that i

Re: DataFrame integration does not support ARRAY type

Hello, Valentin. Yes, this is a bug. Ticket created - https://issues.apache.org/jira/browse/IGNITE-9229 В Вт, 31/07/2018 в 16:01 -0700, Valentin Kulichenko пишет: > Hi Nikolay, > > Can you please take a look at this thread on SO? > https://stackoverflow.com/questions/51621280/saving-a-spark-da

TDE Implementation details.

Hello, Igniters. I want to share with you TDE implementation details. I think it can simplify review and acception of TDE implementation. This mail is copy of wiki page [1]. Please, share your thoughts. TDE is ready for review [2]. Please, let me know, who is able to make final review. This do

C++ Thin client. JVM dependency.

Hello, Igniters. I have a question from one of an early adopter of Ignite C++ thin client. Seems, that our C++ thin client depends on JVM lib. thin-client [1] depends on libignite, and libignite depends on jvm libs [2]. Is that correct? Why do we need it? I thought that a thin client is a binary

Re: DataFrame integration does not support ARRAY type

Dmitriy, I will take care of this ticket in a few days. В Ср, 08/08/2018 в 18:06 -0500, Dmitriy Setrakyan пишет: > Would be nice if someone in the community would pick this ticket up. > > On Wed, Aug 8, 2018 at 1:19 AM, Nikolay Izhikov wrote: > > > Hello, Valentin. > >

Re: Spark SQL Table Name Resolution

Stuart, do you want to work on this ticket? В Вт, 07/08/2018 в 11:13 -0700, Stuart Macdonald пишет: > Thanks Val, here’s the ticket: > > https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-9228 > >

Re: Deprecate force server mode for clients.

+1 from me. В Чт, 09/08/2018 в 12:51 +0300, Pavel Kovalenko пишет: > Andrey, > > Huge +1 for that. > "Force server mode" increases the complexity of understanding how cluster > in ring mode works without real benefits. > If a user wants to start client node first before server nodes have > starte

Re: TDE: Upgrade Team City JDK

:26, Denis Magda wrote: > > > > > > Nikolay, > > > > > > Do you need 8u111 and later? Or any JDK 8 works for you? > > > > > > -- > > > Denis > > > > > > On Tue, Jul 31, 2018 at 6:55 AM Nikolay Izhikov > &

Re: TDE: Upgrade Team City JDK

ill not take tasks from queue automatically, but can > be assigned tasks manually. > > > > On 9 Aug 2018, at 16:27, Nikolay Izhikov wrote: > > > > Hello, Petr. > > > > I'm able to select thi agent for build. > > But it has "disabled" comment.

Re: Apache Ignite 2.7: scope, time and release manager

lov wrote: > > > > Hi Nikolay, > > > > Thank you for this page. It seems font size for some filters is bigger than > > for others. It is intentionally done this way? > > > > Sincerely, > > Dmitriy Pavlov > > > > вт, 31 июл. 2018 г.

Re: TDE: Upgrade Team City JDK

? В Чт, 09/08/2018 в 18:29 +0300, Petr Ivanov пишет: > Done > > > > On 9 Aug 2018, at 17:44, Nikolay Izhikov wrote: > > > > Petr. > > > > Seems, now I has to put my tests in "Basic Tests With Persistence". > > Can you configure Team

Does Ignite support java.sql.Array?

Hello, Igniters. Does Ignite support java.sql.Array? Can someone from SQL experts clarify this case? My question relates to the specific ticket that comes from our user [1], [2] Ignite documentaion says that we support sql ARRAY data type [3]. 1. I'm able to create table with ARRAY column. new

Re: Does Ignite support java.sql.Array?

://issues.apache.org/jira/browse/IGNITE-9230 > > > > On Mon, Aug 13, 2018 at 4:58 PM, Nikolay Izhikov > > wrote: > > > > > Hello, Igniters. > > > > > > Does Ignite support java.sql.Array? > > > Can someone from SQL experts clarify t

Re: ignite PureJavaCrc32 vs java.util.zip.CRC32 bench.

Hello, Denis. AFAIK CRC calculated: 1. For each page that are readed or written to the persistence store [1]. 2. For each read or write of WAL record [2]. [1] https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/file/Fil

Re: Does Ignite support java.sql.Array?

e the steps to > > add Arrays support to the project? I thought this worked all the times. > > > > -- > > Denis > > > > On Mon, Aug 13, 2018 at 8:55 AM Nikolay Izhikov > > wrote: > > > > > Thanks for a comments. > > > > &

<    3   4   5   6   7   8   9   10   11   12   >