Re: binary output from cache

How could it give perfomance improvement ? чт, 9 февр. 2017 г. в 23:21, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Alexey, > > Generally users want to work with their model objects, so we deserialize > them on read by default. BinaryObject API is usually used in more > complicated

Re: IGNITE-13

Hi Vadim, I don't think it makes much sense to invest into OptimizedMarshaller. However, I would check if this optimization is applicable to BinaryMarshaller, and if yes, implement it. -Val On Thu, Feb 9, 2017 at 11:05 PM, Вадим Опольский wrote: > Dear sirs! > > I want

IGNITE-13

Dear sirs! I want to resolve issue IGNITE-13 - https://issues.apache.org/jira/browse/IGNITE-13 Is it actual? Vadim Opolski

Re: DML & Transactions

Updated DML limitations section http://apacheignite.gridgain.org/v1.8/docs/dml#section-transactional-support Feel free to edit if needed. — Denis > On Feb 8, 2017, at 10:20 PM, Yakov Zhdanov

Re: Feedback on Web Console usage

Alex, Good catch. I’ve checked the pom.xml generated by Web Console for the project created with it configuration wizard. The pom downloads 1.7 version. Please let me know once Web Console is updated to 1.8. — Denis > On Feb 9, 2017, at 7:52 PM, Alexey Kuznetsov wrote:

Re: Error in Ignite Web Agent

Prach, Thanks for you help. We will investigate this issue. On Thu, Feb 9, 2017 at 2:28 AM, Prachi Garg wrote: > Hi Alexey, > > I have attached the log, thread dump and heap dump. > > Answer to other questions- > > What operating system you are running? > -OS X El Capitan

Re: Feedback on Web Console usage

Denis, I think I know why you are getting such error. You are using DEMO, and demo is running INSIDE web-agent and web-agent built on ignite-1.7 branch that does not have DML support. We will prepare updated version of web-agent based on ignite-1.8 and it will support DML in DEMO. Meanwhile

Re: Rethink native SQL API in Apache Ignite 2.0

Vladimir, Will these changes be backward compatible? Sergi, given your SQL expertise, can you please comment here as well? D. On Tue, Feb 7, 2017 at 3:34 AM, Vladimir Ozerov wrote: > Igniters, > > Our SQL engine becomes more and more sophisticated. Initially we had only

Re: DML data streaming

On Thu, Feb 9, 2017 at 1:53 AM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > Sergey, > > Streaming does not make sense for INSERT FROM SELECT as this pattern does > not match primary use case for streaming (bulk data load to Ignite). > > Dima, > > No, I suggest that data

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

https://drive.google.com/open?id=0B9teTzJ9iIvHckl6eVQ3N0R4a3c On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin wrote: > I've fixed README.txt and created new DEVNOTES.txt. Also renamed sample > benchmark configuration file to benchmark-sample.properties. > Please look for

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

I've fixed README.txt and created new DEVNOTES.txt. Also renamed sample benchmark configuration file to benchmark-sample.properties. Please look for the results: On Tue, Jan 31, 2017 at 9:18 PM, Denis Magda wrote: > Oleg, > > Thanks for the clarification. > > My opinion is

Re: Patches for Website

Hi Mauricio, I’ve committed the changes. Thanks! — Denis > On Feb 9, 2017, at 9:55 AM, Mauricio Stekl wrote: > > Hi Denis, > I am sorry about that. I have now checked out the repo from trunk/ and built > the patches again. These are attached. > Please let me know if

Re: jdbc vs jdbc2 packages

Yakov, 1. Yes, I will file a ticket. 4. I meant that server can currently initiate connection with client, and that's the main problem here. Is there a way to avoid this? Message routing you're referring to can also be useful in some cases, but much less critical. -Val On Wed, Feb 8, 2017 at

Re: IGNITE-817: [Test] Disabled tests of GridCacheOffHeapTest

Alexander, We use Yardstick benchmarks for performance measurements of Ignite: https://github.com/apacheignite/yardstick-ignite In 1.9 it will be much easier to execute the benchmarks directly from Apache Ignite bundle:

Re: Apache Ignite 1.9

Anton, You can expect Kubernetes support from me in time. — Denis > On Feb 9, 2017, at 1:52 AM, Anton Vinogradov wrote: > > Igniters, > > We're on a half way to Ignite 1.9. > Development phase will be finished 17th of February. > > Here

Re: binary output from cache

Alexey, Generally users want to work with their model objects, so we deserialize them on read by default. BinaryObject API is usually used in more complicated use cases, like when values are read on servers side, or when it gives performance improvement. -Val On Thu, Feb 9, 2017 at 10:36 AM,

Re: Feedback on Web Console usage

Alex, I couldn’t execute DML queries from Web Console. Looks like something was broken if you say it worked before. Try to run the demo mode and execute query like this UPDATE car set parkingid = 20 where id = 12 You will get this error. Error: Unsupported query: UPDATE car set parkingid =

binary output from cache

Guys, i have a dumb question. Why do we need to set withKeepBinary()? What i mean is why dont we just have it hardcoded ? -- *Best Regards,* *Kuznetsov Aleksey*

[GitHub] ignite pull request #1515: IGNITE-4158

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1515 IGNITE-4158 java.sql.Time was implemented in binary protocol You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-4158

[GitHub] ignite pull request #1423: Ignite 4540

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1423 --- 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 #1301: IGNITE-3964: SQL: implement support for table ali...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1301 --- 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 #1406: IGNITE-3867: ScanQuery ignores pageSize property

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1406 --- 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 #1372: IGNITE-4142: Assertion in ClientImpl.updateMetric...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1372 --- 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 #1297: IGNITE-4247: Sql queries supports table alias.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1297 --- 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 #1405: Ignite 1.7.6

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

Hi Vadim. You wrote to Apache Ignite Community dev list. We are glad to hear you want to contribute! But... You a really lucky that considerable part of the community are russian-speakers and can understand you, but there are many people who can't. Would you please resend you questions in

Re: Ensure that builder approach is used for all setters in public API

Wow! This is the regression (from long ago version) if true. As far as having mbean to manage eviction policy on the fly - why not? This is handy. -- Yakov Zhdanov On Feb 9, 2017 9:09 PM, "Andrey Mashenkov" wrote: > Folks, > > I've found no mention in ignite code

[GitHub] ignite pull request #1514: ignite-4664

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/1514 ignite-4664 Added lifecycle and injection support for TopologyValidator. You can merge this pull request into a Git repository by running: $ git pull

IGNITE-13

Здравствуйте, коллеги! Это Опольский Вадим, я недавно в проекте и хочу решить тикет (IGNITE-13). Детализируйте пожалуйста, что конкретно нужно сделать? Где в проекте можно посмотреть примеры уже написанных more optimal marshaling ? Как сейчас маршализируются строки в проекте? Где описаны

IGNITE-817: [Test] Disabled tests of GridCacheOffHeapTest

Hello, everyone. GridCacheOffHeapTest is about the Off-heap benchmarks. As I understand it right now we haven't clear vision how better make benchmarks in Ignite. If it's not true, please make me know. I think it's a good idea to make benchmarks with JMH framework. It can be load with maven,

Re: Ensure that builder approach is used for all setters in public API

Folks, I've found no mention in ignite code where EvictionPolicy used as MBean and it seems it is never registered as MBean. Is it really need to have MBean interfaces for EvictionPolicy implementations? On Wed, Feb 8, 2017 at 7:23 AM, Yakov Zhdanov wrote: > +1 to

[GitHub] ignite pull request #1408: IGNITE-4374

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1408 --- 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: IGNITE-3244

Well, In case of "we should create corresponding array (e.g., String[]) instead of Object[]." doReadObjectArray() method will return Object[] of Binaries if compType is custom class type. But the ticket texts - array must be of object's type, not Object[] чт, 9 февр. 2017 г. в 1:12, Valentin

Re: Test failures

yeah, i will чт, 9 февр. 2017 г. в 0:01, Denis Magda : > > How could they co-exist ? When you developing some ticket you are risking > > introduce bug which is reproduced by already failed test(s). > > Because there is no IT project that is bug-free. In my experience, it’s a >

[GitHub] ignite pull request #1513: IGNITE-4511: Set QueryIndexType.SORTED by default...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1513 IGNITE-4511: Set QueryIndexType.SORTED by default for an index You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: DML & Transactions

Hello everyone. Sergi, you wrote about the MVCC. It's very interesting and perspective. Someone already does it? 2017-02-09 9:25 GMT+03:00 Dmitriy Setrakyan : > On Wed, Feb 8, 2017 at 10:20 PM, Yakov Zhdanov > wrote: > > > Guys, I think we should

[GitHub] ignite pull request #1512: IGNITE-4673 Object array element type is written ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1512 IGNITE-4673 Object array element type is written as a user type You can merge this pull request into a Git repository by running: $ git pull

Re: DML data streaming

Sergey, Streaming does not make sense for INSERT FROM SELECT as this pattern does not match primary use case for streaming (bulk data load to Ignite). Dima, No, I suggest that data streamer mode supports full semantic sense of INSERT (throw an ex if there's a duplicate of PK) optionally and

Re: Apache Ignite 1.9

Igniters, We're on a half way to Ignite 1.9. Development phase will be finished 17th of February. Here is a status page for upcoming release. According to this page we have some Issues we *especially *expect in 1.9:

[GitHub] ignite pull request #1511: Ignite 4671 Fix FairAffinityFunction fails on nod...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1511 Ignite 4671 Fix FairAffinityFunction fails on node restart with backupFilter set and no backups You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-4677) Incorrect connectable node detection in router mode for Java thin client

Andrey Novikov created IGNITE-4677: -- Summary: Incorrect connectable node detection in router mode for Java thin client Key: IGNITE-4677 URL: https://issues.apache.org/jira/browse/IGNITE-4677

Re: Feedback on Web Console usage

Denis, thanks for your feedback. I will take a look and make Web Console more user friendly. Dima, DML is already supported by Web Console because it is SqlFieldsQuery and there no difference from "Select * from Person" and "Delete from person where ID > 500". If DDL will be also implemented

Please review IGNITE-4676

Hi, All! I found a very special bug [1] in Continuation. I debugged it and prepared fix. Test added. Please review [2]. 1. https://issues.apache.org/jira/browse/IGNITE-4676 2. http://reviews.ignite.apache.org/ignite/review/IGNT-CR-91 -- Alexey Kuznetsov