Re: Custom string encoding

Andrey, Can you elaborate more on this? What is your concern? -Val On Fri, Jun 30, 2017 at 6:17 PM Andrey Mashenkov wrote: > Val, > > Looks like make sense. > > This will not affect FullText index, as Lucene has own format for storing > data. > > But.. would it be

Re: Custom string encoding

Val, Looks like make sense. This will not affect FullText index, as Lucene has own format for storing data. But.. would it be compatible with H2 indexing ? I doubt. 1 июля 2017 г. 2:27 пользователь "Valentin Kulichenko" < valentin.kuliche...@gmail.com> написал: > Folks, > > Currently binary

Custom string encoding

Folks, Currently binary marshaller always encodes strings in UTF-8. However, sometimes it can be useful to customize this. For example, if data contains a lot of Cyrillic, Chinese or other symbols, but not so many Latin symbols, memory is used very inefficiently. In this case it would be great to

[jira] [Created] (IGNITE-5655) Introduce pluggable string encoder/decoder

Valentin Kulichenko created IGNITE-5655: --- Summary: Introduce pluggable string encoder/decoder Key: IGNITE-5655 URL: https://issues.apache.org/jira/browse/IGNITE-5655 Project: Ignite

Re: Apache Ignite 2.1 scope

Igniters, It’s time to refresh this abandoned thread and finally rollout out all the changes appeared in 2.1. In addition, recently donated Persistent Store got the green light [1] to become a part of the master branch (no one asked for extra time to dive into its details) and, personally,

Re: Ignite Persistent Store: Ready for merge?

Well, since there are no objections I’ll refresh our discussion about 2.1 releasing considering the persistent store to be released as a part of it. — Denis > On Jun 28, 2017, at 5:54 PM, Dmitriy Setrakyan wrote: > > My vote would be to prepare the donation for the 2.1

Re: Distributed scheduling

I think this functionality should provide durable way of scheduled task or closure execution on the cluster. Job descriptors should be persisted on server side and executed there. As for API, I believe this should be part of Compute Grid. I suggest to introduce

[jira] [Created] (IGNITE-5653) Add to query execution plan debug data for joins

Alexander Paschenko created IGNITE-5653: --- Summary: Add to query execution plan debug data for joins Key: IGNITE-5653 URL: https://issues.apache.org/jira/browse/IGNITE-5653 Project: Ignite

[jira] [Created] (IGNITE-5652) Print slow query warnings on client node

Alexander Paschenko created IGNITE-5652: --- Summary: Print slow query warnings on client node Key: IGNITE-5652 URL: https://issues.apache.org/jira/browse/IGNITE-5652 Project: Ignite

[jira] [Created] (IGNITE-5651) Add long query timeout property

Alexander Paschenko created IGNITE-5651: --- Summary: Add long query timeout property Key: IGNITE-5651 URL: https://issues.apache.org/jira/browse/IGNITE-5651 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5650) Add convenient API for getting column values

Alexander Paschenko created IGNITE-5650: --- Summary: Add convenient API for getting column values Key: IGNITE-5650 URL: https://issues.apache.org/jira/browse/IGNITE-5650 Project: Ignite

[jira] [Created] (IGNITE-5649) REST API, metadata commands always returns list of cache

Aleksandr created IGNITE-5649: - Summary: REST API, metadata commands always returns list of cache Key: IGNITE-5649 URL: https://issues.apache.org/jira/browse/IGNITE-5649 Project: Ignite Issue

Re: [jira] [Created] (IGNITE-5647) Suggestion for Apache Ignite Generic Transactional Receiver Implementation for Concurrency

Hi Fatih, You can find this information here: https://ignite.apache.org/community/contribute.html#ignite-dev -Val On Fri, Jun 30, 2017 at 11:43 AM, fatih wrote: > Hi > > Could please send a guide for a new committer explaining how to create a > branch to the dedicated

Re: DataStreamer Transactional and Timestamp Implementation

Hi Fatih, This makes sense to me, but frankly I don't see anything that can be included in the product here. It's very specific to your case and doesn't add much value in general. Do you have a blog by any chance? :) It looks like a very good topic for an article (describing the use case,

[jira] [Created] (IGNITE-5648) NOT NULL constraint support for CREATE TABLE operator

Denis Magda created IGNITE-5648: --- Summary: NOT NULL constraint support for CREATE TABLE operator Key: IGNITE-5648 URL: https://issues.apache.org/jira/browse/IGNITE-5648 Project: Ignite Issue

Re: [jira] [Created] (IGNITE-5647) Suggestion for Apache Ignite Generic Transactional Receiver Implementation for Concurrency

Hi Could please send a guide for a new committer explaining how to create a branch to the dedicated Jira Ticket and other things that might be necessary? Regards -- View this message in context:

[jira] [Created] (IGNITE-5647) Suggestion for Apache Ignite Generic Transactional Receiver Implementation for Concurrency

fatih created IGNITE-5647: - Summary: Suggestion for Apache Ignite Generic Transactional Receiver Implementation for Concurrency Key: IGNITE-5647 URL: https://issues.apache.org/jira/browse/IGNITE-5647

Re: DataStreamer Transactional and Timestamp Implementation

Hi May I kindly ask if you had a chance to look into the implementation and the use case description in our previous post -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/DataStreamer-Transactional-and-Timestamp-Implementation-tp19129p19312.html Sent

[jira] [Created] (IGNITE-5646) Use affinity keys for distributed matrice blocks

Yury Babak created IGNITE-5646: -- Summary: Use affinity keys for distributed matrice blocks Key: IGNITE-5646 URL: https://issues.apache.org/jira/browse/IGNITE-5646 Project: Ignite Issue Type:

Re: By bytes access to binary format

On Fri, Jun 30, 2017 at 10:35 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Vova, > > Generally this can be useful. If you have a read-only binary object with a > large blob as a field, you don't want to copy this array when reading it. > Instead, we can return a ByteBuffer or

Re: By bytes access to binary format

Vova, Generally this can be useful. If you have a read-only binary object with a large blob as a field, you don't want to copy this array when reading it. Instead, we can return a ByteBuffer or a stream wrapping the corresponding portion. However, I currently don't see how this can be smoothly

[jira] [Created] (IGNITE-5645) Locking mechanism for distributed matrices.

Yury Babak created IGNITE-5645: -- Summary: Locking mechanism for distributed matrices. Key: IGNITE-5645 URL: https://issues.apache.org/jira/browse/IGNITE-5645 Project: Ignite Issue Type: New

[GitHub] ignite pull request #2221: IGNITE-3935

GitHub user Grigory2000 opened a pull request: https://github.com/apache/ignite/pull/2221 IGNITE-3935 Added test for Ignite-3935 issue. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Grigory2000/ignite Ignite-3935 Alternatively

[jira] [Created] (IGNITE-5644) Metrics collection must be removed from discovery thread.

Mikhail Cherkasov created IGNITE-5644: - Summary: Metrics collection must be removed from discovery thread. Key: IGNITE-5644 URL: https://issues.apache.org/jira/browse/IGNITE-5644 Project: Ignite

Re: distributed transaction of non-single coordinator

Thanks! Do you think all test scenarios results, presented in table(in ticket comments) , are acceptable ? пт, 30 июн. 2017 г., 18:28 Yakov Zhdanov : > Alex, I have commented in the ticket. Please take a look. > > Thanks! > -- > Yakov Zhdanov, Director R > *GridGain

[jira] [Created] (IGNITE-5643) REST API, call cache command without cacheName param - got java.lang.NullPointerException

Aleksandr created IGNITE-5643: - Summary: REST API, call cache command without cacheName param - got java.lang.NullPointerException Key: IGNITE-5643 URL: https://issues.apache.org/jira/browse/IGNITE-5643

Re: distributed transaction of non-single coordinator

Alex, I have commented in the ticket. Please take a look. Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2017-06-29 17:27 GMT+03:00 ALEKSEY KUZNETSOV : > I've attached HangTest. I suppose it should not hang, am i right ? > > чт, 29 июн. 2017

Re: Distributed scheduling

On Fri, Jun 30, 2017 at 12:29 AM, Alexey Kuznetsov wrote: > Dmitriy, > > >> Can you provide a simple example of API calls that will make this > possible? > API could be like this: > 1) via scheduler: > Ignite ignite = Ignition.start(); > >

[GitHub] ignite pull request #1975: IGNITE-5113: Implemented basic distributed/local ...

Github user artemmalykh closed the pull request at: https://github.com/apache/ignite/pull/1975 --- 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

[GitHub] ignite pull request #2096: ignite-5383

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2096 --- 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: Request for contributor permission

Hi, Added you to the contributors list. Please go ahead and assign the tickets on yourself. — Denis > On Jun 30, 2017, at 12:10 AM, Александр Метерко > wrote: > > Dear Ignite team, > > I would like to start contributing to your project starting with ticket >

[jira] [Created] (IGNITE-5642) Web Console: improve usability of caches and metadata on Queries screen

Alexey Kuznetsov created IGNITE-5642: Summary: Web Console: improve usability of caches and metadata on Queries screen Key: IGNITE-5642 URL: https://issues.apache.org/jira/browse/IGNITE-5642

[jira] [Created] (IGNITE-5641) Web Console: In addition to export also implement copy result set to clipboard.

Alexey Kuznetsov created IGNITE-5641: Summary: Web Console: In addition to export also implement copy result set to clipboard. Key: IGNITE-5641 URL: https://issues.apache.org/jira/browse/IGNITE-5641

[jira] [Created] (IGNITE-5640) Web Console: when possible do not block UI with modal windows

Alexey Kuznetsov created IGNITE-5640: Summary: Web Console: when possible do not block UI with modal windows Key: IGNITE-5640 URL: https://issues.apache.org/jira/browse/IGNITE-5640 Project:

[jira] [Created] (IGNITE-5639) Web Console: Need to printout time taken evenif result set is empty.

Alexey Kuznetsov created IGNITE-5639: Summary: Web Console: Need to printout time taken evenif result set is empty. Key: IGNITE-5639 URL: https://issues.apache.org/jira/browse/IGNITE-5639

[jira] [Created] (IGNITE-5638) Web Console: Add ability to cancel query

Alexey Kuznetsov created IGNITE-5638: Summary: Web Console: Add ability to cancel query Key: IGNITE-5638 URL: https://issues.apache.org/jira/browse/IGNITE-5638 Project: Ignite Issue

[jira] [Created] (IGNITE-5637) Web Console: Reset previous results when executing new query

Alexey Kuznetsov created IGNITE-5637: Summary: Web Console: Reset previous results when executing new query Key: IGNITE-5637 URL: https://issues.apache.org/jira/browse/IGNITE-5637 Project: Ignite

[jira] [Created] (IGNITE-5636) Web Console: result "set too large" and no info about node on which error occurred and stack trace was unavailable.

Alexey Kuznetsov created IGNITE-5636: Summary: Web Console: result "set too large" and no info about node on which error occurred and stack trace was unavailable. Key: IGNITE-5636 URL:

[jira] [Created] (IGNITE-5635) Web Console: Show query execution progress

Alexey Kuznetsov created IGNITE-5635: Summary: Web Console: Show query execution progress Key: IGNITE-5635 URL: https://issues.apache.org/jira/browse/IGNITE-5635 Project: Ignite Issue

[jira] [Created] (IGNITE-5634) Web Console: add ability to share query notebooks (for token / user)

Alexey Kuznetsov created IGNITE-5634: Summary: Web Console: add ability to share query notebooks (for token / user) Key: IGNITE-5634 URL: https://issues.apache.org/jira/browse/IGNITE-5634

[jira] [Created] (IGNITE-5633) Web Console: Agent hangs on flaky connection to cluster

Alexey Kuznetsov created IGNITE-5633: Summary: Web Console: Agent hangs on flaky connection to cluster Key: IGNITE-5633 URL: https://issues.apache.org/jira/browse/IGNITE-5633 Project: Ignite

[jira] [Created] (IGNITE-5631) Can't write value greater then wal segment

Alexander Belyak created IGNITE-5631: Summary: Can't write value greater then wal segment Key: IGNITE-5631 URL: https://issues.apache.org/jira/browse/IGNITE-5631 Project: Ignite Issue

[jira] [Created] (IGNITE-5630) Exception for node disconnect

Sergey Kozlov created IGNITE-5630: - Summary: Exception for node disconnect Key: IGNITE-5630 URL: https://issues.apache.org/jira/browse/IGNITE-5630 Project: Ignite Issue Type: Bug Affects

[jira] [Created] (IGNITE-5629) .NET: CacheConfiguration copy constructor

Pavel Tupitsyn created IGNITE-5629: -- Summary: .NET: CacheConfiguration copy constructor Key: IGNITE-5629 URL: https://issues.apache.org/jira/browse/IGNITE-5629 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5628) .NET: incorrect jvm.dll lookup paths for JRE

Pavel Tupitsyn created IGNITE-5628: -- Summary: .NET: incorrect jvm.dll lookup paths for JRE Key: IGNITE-5628 URL: https://issues.apache.org/jira/browse/IGNITE-5628 Project: Ignite Issue

RE: golang client for Ignite

Dear Semyon, Thanks. Understood. ((( Thanks, Aleksandr From: Semyon Boikov Sent: 30 июня 2017 г. 10:51 To: dev@ignite.apache.org Cc: Roman Shtykh Subject: Re: golang client for Ignite Hi Aleksandr, Regarding transactions: now implementation of transactions assumes that transaction always

Re: golang client for Ignite

Hi Aleksandr, Regarding transactions: now implementation of transactions assumes that transaction always belongs to some Ignite node, and it seems it is not simple task to support transactions for 'thin' clients. Thanks On Fri, Jun 30, 2017 at 9:55 AM, Aleksandr Sokolovskii

Re: Distributed scheduling

Dmitriy, >> Can you provide a simple example of API calls that will make this possible? API could be like this: 1) via scheduler: Ignite ignite = Ignition.start(); ignite.scheduler().schedulel(job, "0 0 * * *"); // This will execute job every day at 00:00 2) via compute Ignite ignite =

[GitHub] ignite pull request #1930: logging of memory configuration improvements on n...

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

Request for contributor permission

Dear Ignite team, I would like to start contributing to your project starting with ticket https://issues.apache.org/jira/browse/IGNITE-5592 . Could you grant me permissions in Jira to assign this ticket to me? My login is ameterko. Thanks in advance.

RE: golang client for Ignite

Dear Vladimir, Thanks for your answer. Now I understand the difference between ‘client’ and ‘thin client’. Just to be clear I develop ‘thin client’ for DataGrid now: https://github.com/amsokol/go-ignite-client and all my questions are in context of ‘thin client’. So the questions are: 1) Does