affinity key syntax

Igniters, Please take a look at how the affinity syntax works in Google Spanner: https://stackoverflow.com/questions/46903159/can-i-have- multiple-tables-with-same-parent-in-google-spanner I find it rather nice. Perhaps we can borrow from it. D.

Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

It looks like the case sensitivity for the affinity key is a bug. Vladimir, what do you think? On Mon, Oct 23, 2017 at 11:19 AM, Denis Magda wrote: > Vladimir, thanks a lot for looking into this! > > > On Oct 23, 2017, at 12:35 AM, Vladimir Ozerov >

Re: How to turn our Nabble list into forums-based community with roles & ranks (gamification) + social media options

Hi Tim, I have tried the Board application type, but it will not work for us. We really need to continue using the Forum application type, in which case your proposed macro does not make sense. I did add the social medial buttons though. D. On Fri, Oct 20, 2017 at 11:00 AM, Tom Diederich

Re: sql documentation

e > a > >> bit and propose other solutions. > >> > >> — > >> Denis > >> > >> On Sep 13, 2017, at 3:41 AM, Serge Puchnin <sergey.puch...@gmail.com> > >> wrote: > >> > >> I have done some reorganizing for the SQL

Re: SQL error codes

On Thu, Oct 19, 2017 at 2:48 PM, Alexander Paschenko < apasche...@gridgain.com> wrote: > Dmitriy, > > There are Ignite specific codes, they are returned when queries are run > via Ignite API. There are no codes explicitly shared by JDBC and ODBC, > although some of them happen to be the same. >

Re: SQL error codes

On Thu, Oct 19, 2017 at 9:48 AM, Vladimir Ozerov wrote: > No, they are not re-used. SQLSTATE is JDBC/ODBC-specific thing (and both > driver types have different codes). > Vladimir, are there any error codes that come from the Ignite engine that are shared between JDBC and

Re: Adding sqlline tool to Apache Ignite project

On Wed, Oct 18, 2017 at 11:30 PM, Vladimir Ozerov wrote: > Igniters, > > We named the script "Ignitesql.sh" because initially we thought that it > would have additional logic. But now it is merely a thin wrapper around > sqlline which only contains classpath creation logic

Re: Persistence per memory policy configuration

iption of https://issues.apache.org/jira > /browse/IGNITE-6030, I've updated it with actual list of properties. > > Best Regards, > Ivan Rakov > > > On 17.10.2017 21:46, Dmitriy Setrakyan wrote: > >> I am now confused. Can I please ask for the final configuration again? >> What &g

Re: Integration of Spark and Ignite. Prototype.

Val, thanks for the review. Can I ask you to add the same comments to the ticket? On Tue, Oct 17, 2017 at 3:20 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Nikolay, Anton, > > I did a high level review of the code. First of all, impressive results! > However, I have some

Re: Clarification on DROP TABLE command needed

Vladimir, Is the cache purged synchronously or in the background? D. On Tue, Oct 17, 2017 at 12:10 AM, Vladimir Ozerov wrote: > Hi Denis, > > 1) Yes, cache is destroyed and data is purged. > 2) We acquire table lock, so that DML and SELECT statements will be blocked >

Re: Persistence per memory policy configuration

dex storage and WAL are located under the same root by default. > >>>> However, this is not mandatory: *storagePath* and *walPath* properties > >>>> > >>> can contain both absolute and relative paths. If paths are absolute, > >>> st

Re: [Ignite 2.3 release]: Java 9 in compatibility mode

On Tue, Oct 17, 2017 at 9:11 AM, Denis Magda wrote: > Considering the scope of the work to be done it sounds reasonable to move > this task to the next release. Anyway, Java 9 was released just a couple of > weeks ago and it’s normal to spend some time for the code adaptation

Re: Persistence per memory policy configuration

; > >>> > > >>> Denis, > > >>> > > >>> Data/index storage and WAL are located under the same root by > default. > > >>> However, this is not mandatory: *storagePath* and *walPath* > properties > > >> can contai

Re: Indexing fields of non-POJO cache values

On Mon, Oct 16, 2017 at 12:35 PM, Andrey Kornev wrote: > [Crossposting to the dev list] > > Alexey, > > Yes, something like that, where the "reference"/"alias" is expressed as a > piece of Java code (as part of QueryEntity definition, perhaps) that is > invoked by

Re: Optimized DML execution: how to name it?

On Mon, Oct 16, 2017 at 12:15 AM, Vladimir Ozerov wrote: > Dmitriy, > > No :-) System properties is bad practice, because in some cases you cannot > change them. Instead, this flag is available in private class > SqlFIeldsQueryEx. So in case user desperately need it, we may

Re: Optimized DML execution: how to name it?

On Sun, Oct 15, 2017 at 12:27 AM, Vladimir Ozerov wrote: > No, it is not exposed to public API. Didn't want to add another flag to > SqlFieldsQuery. > I think we should add a system property. This way you don't have to add any API flags. Agree?

Re: Optimized DML execution: how to name it?

Vova, is there any way to enable this flag from API, without using JDBC driver? On Sat, Oct 14, 2017 at 1:17 PM, Vladimir Ozerov <voze...@gridgain.com> wrote: > Dmitry, > > Corretct. Example: jdbc:ignite:thin://192.168.0.1?skipReducerOnClient=true > > On Fri, Oct 13, 201

Re: Optimized DML execution: how to name it?

Vova, Just to make sure, we are not adding a new configuration property, right? Is this just a JDBC connection flag we are discussing? If yes, can you please provide an example of the JDBC connection string? D. On Fri, Oct 13, 2017 at 9:57 AM, Denis Magda wrote: > Vladimir,

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

message. If we do not deserialize here, we > > won't > > > > > process this message as failed. What way to resolve it? I see we > can > > > try > > > > to > > > > > deserialize after a check on Externalizable in a finishUnmarshall > > > meth

Re: Time units of AverageTxCommitTime and AverageTxRollbackTime in CacheMetrics.

Absolutely, create a ticket. It would be even better if you picked it up and contributed a fix :) On Wed, Oct 11, 2017 at 6:06 AM, Pavel Pereslegin wrote: > Hello, Igniters. > > > I found that AverageTxCommitTime and AverageTxRollbackTime metrics in > CacheMetrics calculated

Re: Context switching for pessimistic transactions

On Wed, Oct 11, 2017 at 9:00 AM, ALEKSEY KUZNETSOV wrote: > Hi, Igntrs! > > For suspend\resume operations in pessimistic mode we want to write the same > tests as for optimistic mode. > > What additional tests should we create for the task? Alexey, I think you should

Re: Persistence per memory policy configuration

On Thu, Oct 12, 2017 at 7:01 PM, Denis Magda wrote: > From what I see after running an example they are under the same root > folder and in different subdirectories. The root folder should be defined > by setPersistencePath as I guess. > If that is the case, then you are

Re: Optimized DML execution: how to name it?

On Wed, Oct 11, 2017 at 11:45 PM, Vladimir Ozerov wrote: > Igniters, > > We prepared optimization of DML processing. Instead of passing all data > being updated through the client node, now we can optionally send SQL > statement to data nodes and perform update locally.

Re: Persistence per memory policy configuration

se both WAL and > index/partition files storage provide persistence. That's why we separated > API methods as *setWalPath* and *setStoragePath*. > > I think, *setStoragePath* is good enough as long as it's supported by > explaining javadoc.* > > * > > > > Best Re

Re: Persistence per memory policy configuration

>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>

Re: OpenSSL licence compatibility

The license looks very much like FreeBSD license [1] with additional clauses. I doubt that ASF will be receptive to the additional restriction clauses in the license. However, I came across this OpenSSL blog [2] which states that they are relicensing under Apache v.2.0 license. If you are willing

Re: Refactoring of IgniteKernal ack methods

On Wed, Oct 11, 2017 at 7:44 AM, Иван Федотов wrote: > Hello, Igniters! > > I found, that in several places of IgniteKernal class code blocks are huge > and hard to understand and in other places methods have the same context > and could be placed in their own class. For

Re: Why SQL_PUBLIC is appending to Cache name while using JDBC thin driver

ugh to identify a table. Currently, using your words, the solution looks like a "hack". Why not just remove the prefix and check for uniqueness within a schema? D. > > On Mon, Oct 9, 2017 at 9:21 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > On M

Re: Why SQL_PUBLIC is appending to Cache name while using JDBC thin driver

On Mon, Oct 9, 2017 at 1:27 AM, Vladimir Ozerov <voze...@gridgain.com> wrote: > Hi Dima, > > To maintain unique cache names across the cluster. > Why not simply check for uniqueness at creation time? Why introduce some automatic prefix? > > On Mon, Oct 9, 2017 at 7:

Re: Download links on ignite.apache.org not always working

Ilya, I do not see this mirror in the list. Do you still see it? If yes, we can try filing an INFRA issue in JIRA. D. On Mon, Oct 9, 2017 at 10:00 AM, Ilya Kasnacheev wrote: > Hello Igniters, > > It came to my attention that I am offered to download >

Fwd: Why SQL_PUBLIC is appending to Cache name while using JDBC thin driver

Cross-sending to dev@ Why do we need to append SQL_PUBLIC_ to all table names? D. -- Forwarded message -- From: Denis Magda Date: Sun, Oct 8, 2017 at 7:01 AM Subject: Re: Why SQL_PUBLIC is appending to Cache name while using JDBC thin driver To:

Re: Adding sqlline tool to Apache Ignite project

r more > information. > > ./ignitesql.sh 192.168.12.55 > > Connected successfully. > > Again, specifying parameters manually is not poor UX. This is excellent UX, > as user learns on his own how to connect to a node in 1 minute. Most > command line tools work this way. > &g

Re: Adding sqlline tool to Apache Ignite project

inclusion in Ignite’s binary releases > >>>>> let’s > >>>>>>> create a shell script to simplify the connectivity phase: > >>>>>>> > >>>>>>> - name the script as ignitedb.sh for Unix and ignitedb.bat for >

Re: Adding sqlline tool to Apache Ignite project

On Fri, Oct 6, 2017 at 9:04 AM, Anton Vinogradov wrote: > How about sqlconsole.sh or sqlcmd.sh ? > Shouldn't we have "ignite" in the name?

Re: Context switching for pessimistic transactions

Thanks, Alexey. I doubt anyone in the community will be able to answer your question here. I am assuming that thread ID is not going to be enough to identify a transaction, given that suspend happens in one thread, and resume in another. However, to tell for sure would require a better

Re: Adding sqlline tool to Apache Ignite project

Would be nice to get it in 2.3. This is critical functionality for our users and 2.4 seems too far to give anyone comfort. On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov wrote: > Guys, > > I've created the ticket for 2.4 release: >

Re: Monitoring of active transactions

on > classpash) > > Good for admin's console scripting. > > 2) binary rest api by some java tool (with instant peerClassLoading). > Good > > for investigation on any grid configuration. > > 3) maybe, by client node as it implemented now (can't see any adwantages) > > > &

Re: documentation suggestions

ible. D. On Thu, Oct 5, 2017 at 12:07 AM, Denis Magda <dma...@apache.org> wrote: > Please see inline > > > On Oct 4, 2017, at 5:17 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > > I would like to propose some changes to the Ignite do

Re: PRIMARY_SYNC+readFromBackup semantics

Val, do you have a fix in mind? On Thu, Oct 5, 2017 at 2:50 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > FULL_SYNC as default is not a solution. PRIMARY_SYNC/readFromBackup is > valid combination of parameters and useful in many scenarios. For example, > what if I have a

Re: Identifying grid transactions

On Wed, Oct 4, 2017 at 3:01 PM, Konstantin Dudkov wrote: > Hi, > > .withTag maybe? > Agree, withTag() looks much better.

documentation suggestions

I would like to propose some changes to the Ignite documentation: - Under Basic Concepts add the following pages: - "How to load data" - "SQL vs Scan" - "SQL vs Key-Value" - more? - For persistence section, add the following pages: - Write-Ahead-Log (WAL)

Re: Identifying grid transactions

I would rename to "withMetadata()". On Wed, Oct 4, 2017 at 2:31 PM, Vladimir Ozerov wrote: > Alex, > > I do not think we have such feature in the product at the moment. But this > could be very valuable addition. For example, we have somewhat similar task > for JDBC - to

Re: [DISCUSS] Ignite Update Checker

e/INFRA-15182 < > https://issues.apache.org/jira/browse/INFRA-15182> > > — > Denis > > > On Oct 2, 2017, at 2:48 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > > On Mon, Oct 2, 2017 at 12:46 PM, Vladimir Ozerov <voze...@gridgain.com> &g

Re: Persistence per memory policy configuration

On Mon, Oct 2, 2017 at 7:28 PM, Denis Magda wrote: > > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > > > > In other data regions persistence

Re: [DISCUSS] Ignite Update Checker

l <https://repo1.maven.org/ > > maven2/org/apache/ignite/ignite-core/maven-metadata.xml> > > > > > > > 2 окт. 2017 г., в 12:51, Dmitriy Setrakyan <dsetrak...@apache.org> > > написал(а): > > > > > > Denis, > > > > > > I am not sure I un

Re: [DISCUSS] Ignite Update Checker

r sever side language and trigger GA as discussed earlier: > https://issues.apache.org/jira/browse/INFRA-15182 > > How else can we tackle this? > > Denis > > On Thursday, September 7, 2017, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > I think it is safe

Re: Persistence per memory policy configuration

On Mon, Oct 2, 2017 at 7:46 AM, Denis Magda wrote: > > > On Oct 1, 2017, at 4:41 AM, Ivan Rakov wrote: > > > > 1) You're right. I forgot to include the main flag in > DataRegionConfiguration - *isPersistenceEnabled*. Persistence will be > enabled

Re: Persistence per memory policy configuration

>>> https://issues.apache.org/jira/browse/IGNITE-6030 >>> Please, take a look. Right now is the best time to change name of any >>> property. >>> >>> And question about metrics: are we going to rename MemoryMetrics and >>> PersistenceMetrics respectiv

Re: Future of Ignite transactions

On Fri, Sep 29, 2017 at 8:16 AM, Yakov Zhdanov wrote: > I agree with Vladimir here. I always have some awkward feelings when > explaining our optimistic transactions behavior. Let's fix it now. > In that case, let's try to come up with a cleaner proposal. The new design has

Re: Future of Ignite transactions

On Fri, Sep 29, 2017 at 6:10 AM, Vladimir Ozerov wrote: > Dima, > > I doubt you ever heard from users "we need snapshot isolation" because this > is implementation detail, rather than public behavior :-) > Believe me, I have. People want to make sure that the data is not

Re: Future of Ignite transactions

" reads is relatively rare > use case comparing to "optimistic". This is why "with" approach looks > better to me. > > Blocking reads doesn't make sense outside of explicit transaction. > > On Fri, Sep 29, 2017 at 3:47 PM, Dmitriy Setrakyan <dsetrak

Re: Future of Ignite transactions

or on TX level. They do that on per-operation > level. > In that case, why do you suggest the "with" API which will set this flag for all operations. Why not just add "getWithLock()" method? Also, will this method work on non-transactional caches? > > On Fri, Sep 29,

Re: Issues if -Djava.net.preferIPv4Stack=true is not set

Hm... I am not sure I understand why. But in any case, to the list, we should provide proper error messages suggesting to change this property. Do you agree? D. On Fri, Sep 29, 2017 at 3:18 AM, Yakov Zhdanov wrote: > If user has Ignite deployment and does not want Ignite

Re: Future of Ignite transactions

On Thu, Sep 28, 2017 at 10:30 PM, Vladimir Ozerov wrote: > Dima, > > IgniteCache.withReadForUpdate() :-) > And how is it better than a pessimistic transaction with read?

Re: Support for packed int and long primitives in raw binary API

Alexey, are you talking about arrays of ints and longs? On Fri, Sep 29, 2017 at 3:29 AM, Alexei Scherbakov < alexey.scherbak...@gmail.com> wrote: > Guys, > > I notices we do not have support for packed ints and longs in raw binary > API [1] [2] > > Such methods are essential for implementing

Re: Future of Ignite transactions

roper implementation allows to achieve better isolation without blocking > > for the cost of additional resource consumption. > > > > The feature can be configurable per transaction. > > > > 6) What if I want to acquire write locks only for some specific reads > &

Re: Issues if -Djava.net.preferIPv4Stack=true is not set

On Thu, Sep 28, 2017 at 7:08 AM, Yakov Zhdanov wrote: > The issue has already been picked up by VK. > > Dmitry, after some thought I find it a little bit weird to set system > property automatically without any way to restore default behavior. > I am not sure I understand.

Re: Issues if -Djava.net.preferIPv4Stack=true is not set

On Wed, Sep 27, 2017 at 5:08 AM, Yakov Zhdanov wrote: > hmm.. Dmitry, your suggestion may work if Ignite is started before any of > network layer class is loaded/called. E.g. this will not work if Ignite is > started inside application or web server. > Sure, let's do it

Re: Future of Ignite transactions

which > is perfectly aligned with upcoming transactional SQL. > The API does not look clean yet. Still requires lots of work. > > Thoughts? > > > On Thu, Sep 7, 2017 at 6:48 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > Vova, > > >

Re: [DISCUSS] Ignite Update Checker

ompatibility or spotting bugs for a certain release. Cos, Raul, any thoughts? > > > Vladimir. > > On Fri, Sep 8, 2017 at 7:06 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > I think it is safe to assume at this point that everyone is in general > >

Re: Persistence per memory policy configuration

tion as well. > > вт, 26 сент. 2017 г. в 17:27, Dmitriy Setrakyan <dsetrak...@apache.org>: > > > Dmitriy, we are not renaming classes, we are refactoring them. Prior to > > this design, it was impossible to set persistence configuration on > > per-cache bas

Re: Issues if -Djava.net.preferIPv4Stack=true is not set

Why don't we automatically set the preferIPv4Stack to true, unless the user explicitly set it to false? D. On Tue, Sep 26, 2017 at 4:35 AM, Yakov Zhdanov wrote: > Val, I see now. > > For example, this http://apache-ignite-users.70518.x6.nabble.com/How- >

Re: Future of Ignite transactions

hether to spend time on internals or not. > We will have to do that anyway. > > On Tue, Sep 26, 2017 at 9:02 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > Vladimir, > > > > I do not think we have a luxury of changing Ignite transaction APIs. It >

Re: Future of Ignite transactions

ERIALIZABLE). This make our API very hard to explain and > reason about. If you cannot explain API in 5 mins, it is broken :-) > > If we were many years in the past allowed to choose between Ignite and SQL > approaches I would prefer SQL because it is much simpler. > > On Tue, Sep 26

Re: Persistence per memory policy configuration

I would prefer to have either [StoreConfiguration + > StoreRegionConfiguration] or [PageStoreConfiguration and > PageStoreRegionConfiguration]. Looks clean and simple. > > Vladimir. > > > On Mon, Sep 25, 2017 at 3:49 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote:

Re: Future of Ignite transactions

5 minutes, instead of current half an hour. And which > is perfectly aligned with upcoming transactional SQL. > > Thoughts? > > > On Thu, Sep 7, 2017 at 6:48 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > Vova, > > > > Thanks for doin

Re: Warning if no table for BinaryObject

On Fri, Sep 22, 2017 at 9:47 AM, Mikhail Cherkasov wrote: > Hi all, > > I've seen several times that due wrong cache configuration people can't > find > data in cache and blame Ignite that it's buggy and doesn't work. > > And it's very difficult to find an error in the

Re: Persistence per memory policy configuration

he.org/jira/browse/IGNITE-6030 and proceed with > the changes. > > 2017-09-23 17:08 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > > > Can we specify what metrics will look like? I think we should not just > > blindly merge them. > > > > On Fri, Sep

Re: Persistence per memory policy configuration

https://ignite.apache.org/releases/latest/javadoc/org/ > > apache/ignite/MemoryMetrics.html <https://ignite.apache.org/ > > releases/latest/javadoc/org/apache/ignite/MemoryMetrics.html> > > [2] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/ > > Persiste

Re: Persistence per memory policy configuration

eans. > > What we have in the end: > > > > > > > > > > > > > > > > > >

Re: Persistence per memory policy configuration

Firstly all, why not call it DataPolicy instead of MemoryPolicy? Secondly, why not set data policies directly on IgniteConfiguration. And lastly, how about we combine memory and disk properties in one bean with clear naming convention? Here is the example. Note that all properties above must

Re: Disabling ODBC/thin JDBC/thin .NET connectivity

On Wed, Sep 20, 2017 at 6:37 AM, Igor Sapego wrote: > For example, some users may want to disable clients they are not > using due to security considerations. > Well, there should be some authentication command in the protocol, which will ask a client to login. Ignite should

Re: Disabling ODBC/thin JDBC/thin .NET connectivity

Why do we need the ability to disable individual clients? On Wed, Sep 20, 2017 at 5:26 AM, Igor Sapego wrote: > I've filed a ticket for that: [1] > > [1] - https://issues.apache.org/jira/browse/IGNITE-6456 > > Best Regards, > Igor > > On Wed, Sep 20, 2017 at 2:33 PM,

Re: MVCC configuration

On Tue, Sep 19, 2017 at 11:31 PM, Semyon Boikov wrote: > > Can caches within the same group have different MVCC configuration? > > Do you think we really need have in the same group caches with different > mvcc configuration? for simplicity I would do not allow this. > I

Re: MVCC configuration

Can caches within the same group have different MVCC configuration? On Tue, Sep 19, 2017 at 2:34 AM, Vladimir Ozerov wrote: > What I mean is that it might be not applicable for DML by design. E.g. may > be we will have to fallback to per-memory-policy approach, or to >

Re: Ignite Enhancement Proposal process

Great idea. Either name is fine by me, but we badly need to add these Wiki pages ASAP. Here are some candidates: - Usability - SQL - MVCC - Persistence - Performance D. On Tue, Sep 19, 2017 at 6:00 AM, Vladimir Ozerov wrote: > Both "improvement" and "enhancement" are OK

Re: MVCC configuration

On Mon, Sep 18, 2017 at 2:39 AM, Semyon Boikov wrote: > > 1. MVCC will definitely bring some performance overhead, so I think it > should not be enabled by default, I'm going to add special flag on cache > configuration: CacheConfiguration.isMvccEnabled. > Is it possible for

Re: MVCC configuration

On Mon, Sep 18, 2017 at 4:57 AM, Vladimir Ozerov wrote: > Alex, > > With putAll() on ATOMIC cache all bets are off, for sure. > Are we all in agreement that MVCC should only be enabled for transactional caches then?

Re: Issues if -Djava.net.preferIPv4Stack=true is not set

Any comments here? Do we really require IPv4 for some reason? On Mon, Sep 18, 2017 at 9:51 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Guys, > > I noticed there are many issues on user forum that occur > of -Djava.net.preferIPv4Stack=true system property is not set. > > Can

Re: Ignite PDS WAL analysis with human readable records

de .conf file to configure reader once. > > Sincerely, > Dmitriy Pavlov > > пн, 18 сент. 2017 г. в 16:10, Dmitriy Setrakyan <dsetrak...@apache.org>: > > > Thanks! > > > > After looking at the ticket, the way to launch this utility seems > complex. > &

Re: Ignite PDS WAL analysis with human readable records

1000c000f, > effectivePageId=000c000f, grpId=2141373875], page = [ > Header [ > type=20 (PagePartitionCountersIO), > ver=1, > crc=0, > pageId=281526516318223(offset=0, flags=1, partId=12, index=15) > ], > PagePartitionCounters [ > count=1, > lastFlag=

Re: Ignite PDS WAL analysis with human readable records

Can we get a sample print out from this utility? On Sun, Sep 17, 2017 at 3:42 PM, Eduard Shangareev < eduard.shangar...@gmail.com> wrote: > Dmitry, > thank you for starting this topic. > > The IDEA of this utility is very simple - get the possibility to look into > your WAL. > But it also

Re: Ignite Benchmarking Rules

e - Which hardware is best for > > Ignite benchmarking? > > > > I found some numbers here - [1]. Is it well suited for Apache Ignite? > > > > [1] https://www.gridgain.com/resources/benchmarks/gridgain-vs- > > hazelcast-benchmarks > > > > 14.09.2017 23:27, D

Re: Monitoring of active transactions

It seems that the community (including me) really would like to see this feature in Ignite. Ilya, can you create a ticket and submit it for review? D. On Fri, Sep 8, 2017 at 7:15 AM, Anton Vinogradov wrote: > Ilya, > > We extremely need this! > > Txs and Locks info should be

Re: [VOTE] Apache Ignite 2.2.0 RC1

Igniters... at this point this is becoming almost amusing to watch. All we aimed to do is fix one issue with memory consumption, then bunch of community members started pouring in other fixes into this "emergency" release, and as a result, nothing works. I propose to go back to the original goal

Re: Ignite Benchmarking Rules

Alexey, I completely agree. However, for the benchmarks to be useful, then need to be run on the same hardware all the time. Apache Ignite does not have servers sitting around, available to run the benchmarks. Would be nice to see how other projects address it. Can Amazon donate servers for the

Re: Ignite.NET static analysis with NDepend

Pavel, nice blog! If there is a way to integrate nDepend into Ignite builds, would be nice. D. On Thu, Sep 14, 2017 at 6:38 AM, Pavel Tupitsyn wrote: > Igniters, > > NDepend [1] has contacted me and provided us with build machine licenses > for their tool. > I've played

Re: Static code analysis for Java

Hm... LGTM tool looks nice! Check out all the errors it already found in Ignite :) https://lgtm.com/projects/g/apache/ignite/alerts/?mode=list=error D. On Thu, Sep 14, 2017 at 9:21 AM, Pavel Tupitsyn wrote: > Yes, we can run IDEA inspections, and this is the simplest

Re: Durable Memory and Ignite Persistence Tuning

Completely agree with Nikita. Why not add this information here? https://apacheignite.readme.io/docs/durable-memory-tuning D. On Wed, Sep 13, 2017 at 2:54 AM, Nikita Ivanov wrote: > Excellent work on this... This should be expanded and be prominently placed > in our

Re: Experimental features - thin client protocol as a first candidate

Vladimir, As far as the client, I don't think we need to call it experimental. An "experimental" feature sounds like it might explode if you come close :) How about we have client protocol versions instead? Then each Ignite release can announce which protocol versions it is compatible with. D.

Re: Expiry policy for Cache.invoke

Denis, I agree that the behavior should be consistent, but you will not find anything about transactions in JCache. To my knowledge, JCache does not have transactions. I would file a ticket about the issue you found, so the community could address it. If you are interested, perhaps you can

Re: Specifying schema name with thin JDBC driver

Vova, I think we need to abandon this "schema-name = table name" legacy. It is impossible to explain. Also, I would like to understand the current behavior. When I connect through JDBC, which schema am I connecting to? How do I know which schemas are there? D. On Wed, Sep 13, 2017 at 1:19 AM,

Re: guard() and checkClusterState() checks in Ignite Kernal

Is there a ticket for this change? On Tue, Sep 12, 2017 at 4:25 AM, Ilya Kasnacheev wrote: > Rehi, > > After some discussions https://github.com/apache/ignite/pull/2526 seems to > have correct changeset that covers two methods which seem to have been > overlooked

Re: sql documentation

017 at 02:19, Denis Magda <dma...@apache.org> wrote: > > > Please check you inbox. > > > > — > > Denis > > > > > On Sep 8, 2017, at 3:38 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > > wrote: > > > > > > Denis, > &

Re: New thin client and interfaces/facades

Vladimir, I disagree. We already have client mode which support the full Ignite API. Here we are talking about the new client binary protocol. To my knowledge, the following APIs can be implemented over the new binary protocol: - JDBC - ODBC - REST - .NET Thin All these protocols are already

Re: ContinuousQueryWithTransformer implementation questions - 2

Vladimir, are their factories for the proposed listeners? On Tue, Sep 12, 2017 at 7:52 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Vladimir, > > Can you please clarify how the proposed API will work? > > My opinion is that our query API is big piece of ... you know, especially >

Re: How to configure new thin client connector on the server?

On Tue, Sep 12, 2017 at 1:50 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > In my opinion all clients, including JDBC, ODBC, and REST should be > > implemented over the same protocol and we should not have the protocol > mess > > we have today. >

Fwd: Re: When cache node switch between primary and backup any notification be received?

: Dmitriy Setrakyan <dsetrak...@apache.org> Date: Mon, Sep 11, 2017 at 10:41 PM Subject: Re: Re: When cache node switch between primary and backup any notification be received? To: user <u...@ignite.apache.org> Cc: aa...@tophold.com On Mon, Sep 11, 2017 at 6:54 PM, aa...@tophold.com <aa

Re: AffinityKeyMapper alternatives

On Mon, Sep 11, 2017 at 4:47 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Even if CacheKeyConfiguration is part of CacheConfiguration, the affinity > key field name can be provided only on cache startup. In many cases this > name can be resolved only based on the actual key

Re: Ignite Benchmarking page on readme.io

On Mon, Sep 11, 2017 at 6:10 PM, Denis Magda wrote: > 1. It’s fine to have it under the current section that will include > testing related documentation proposed by Yakov in other discussion thread. > I think we should avoid having 1-page sections. They look bad. Also,

<    1   2   3   4   5   6   7   8   9   10   >