Re: IGNITE-4487 - NPE on query execution

Alexander, I left my comments in the ticket. 2017-01-06 20:35 GMT+03:00 Denis Magda : > Thanks Alexander. > > Someone will review and merge your changes in the nearest time. Alex G., > can you do that? > > — > Denis > > > On Jan 6, 2017, at 5:07 AM, Александр Меньшиков > wrote: > > > > http://c

[jira] [Created] (IGNITE-4531) Update DML operation not working for QuerySQLField with name

David Albrecht created IGNITE-4531: -- Summary: Update DML operation not working for QuerySQLField with name Key: IGNITE-4531 URL: https://issues.apache.org/jira/browse/IGNITE-4531 Project: Ignite

Extend TcpDiscoveryVmIpFinder functionality

Hi Igniters I found that TcpDiscoveryVmIpFinder could be improved for Spring configuration by introducing new format: *address/mask:port(port range) or address/prefix:port(port range)*. From my standpoint it will reduce the efforts for ignite deployment and administration. For instance if we've a

[jira] [Created] (IGNITE-4532) .NET: Fix build warnings

Pavel Tupitsyn created IGNITE-4532: -- Summary: .NET: Fix build warnings Key: IGNITE-4532 URL: https://issues.apache.org/jira/browse/IGNITE-4532 Project: Ignite Issue Type: Task Comp

[GitHub] ignite pull request #1405: Ignite 1.7.6

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1405 Ignite 1.7.6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.7.6 Alternatively you can review and apply the

Re: Extend TcpDiscoveryVmIpFinder functionality

Sergey, This could be very dangerous in terms of node startup time. The very first node in topology will have to scan the whole range trying to find any other node. It might take significant time not only on Windows, but on Linux environments as well, especially when some addresses are not availab

Re: Extend TcpDiscoveryVmIpFinder functionality

Agree with Vladimir. However, this functionality maybe useful in some cases. As far as I remember we support port range notation, e.g. 127.0.0.1:47500..47509, but we don't have this for addresses. If we implement this I would suggest the same approach, e.g 192.168.0.1..5:47500 Thoughts? --Yakov

Re: Extend TcpDiscoveryVmIpFinder functionality

+1 On Mon, Jan 9, 2017 at 2:11 PM, Yakov Zhdanov wrote: > Agree with Vladimir. > > However, this functionality maybe useful in some cases. As far as I > remember we support port range notation, e.g. 127.0.0.1:47500..47509, but > we don't have this for addresses. If we implement this I would sugg

[GitHub] ignite pull request #1401: IGNITE-4412 fix NLogLoggerTest thread safety issu...

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

Re: Contributing to Ignite.NET

Sergey, I've merged your fix for IGNITE-4412. Looking forward to more contributions from you! Pavel On Thu, Jan 5, 2017 at 8:15 PM, Pavel Tupitsyn wrote: > Hi Sergey, > > I've added you to project contributors in Jira. > > I can suggest the following .NET tickets to get familiar with the proje

[GitHub] ignite pull request #1078: IGNITE-3867: ScanQuery ignores pageSize propertry

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1078 --- 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 AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1406 IGNITE-3867: ScanQuery ignores pageSize property Fixed. Test added. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignit

[GitHub] ignite pull request #1407: IGNITE-3430 .NET: Run Ignite transactions via sta...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1407 IGNITE-3430 .NET: Run Ignite transactions via standard TransactionScope API You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-i

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

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1408 IGNITE-4374 Check of "Basic JVM Configuration" added. Link to the tuning article added. https://apacheignite.readme.io/docs/jvm-and-system-tuning You can merge this pull request into a Gi

[GitHub] ignite pull request #1409: Ignite 4219

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1409 Ignite 4219 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4219 Alternatively you can review and apply the

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

Roman, perfect! Well done! *Prachi*, please add Roman’s blog to Apache Ignite’s blogs list: https://ignite.apache.org/blogs.html *Sally*, considering that all the information is already at place is it a good time to wrap it up in an Apache official announce

Adding blog posts to Apache Ignite's blogs list

Hi Shamim, Suddenly I came across your personal blog that has a lot of thoughtful and well-detailed Apache Ignite posts. http://frommyworkshop.blogspot.ru If you don’t mind we will your latest post about the published Ignite book to Ignite’s blog list. BTW,

[GitHub] ignite pull request #1410: ignite-4499

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/1410 ignite-4499 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-4499 Alternatively you can review and apply these chan

Re: Extend TcpDiscoveryVmIpFinder functionality

Hi Thanks Yakov and Vladimir! In general I'm ok for Yakov's suggestion though a bit not clear why discovery by network mask will take long time. Is the discovery spi single-threaded and Ignite processes the addresses consequentially? On Mon, Jan 9, 2017 at 2:39 PM, Vladimir Ozerov wrote: > +1

Re: Adding blog posts to Apache Ignite's blogs list

Good evening, Denis, The direct URL of the post is as follows: http://frommyworkshop.blogspot.ru/2016/09/book-high-performance-in-memory.html If I will have any new post, I will let you know about it. With best regards Shamim Ahmed > On 9 янв. 2017 г., at 21:48, Denis Magda wrote: > > Hi S

Re: Adding blog posts to Apache Ignite's blogs list

I just bought the book. Looking forward to reading it. On Mon, Jan 9, 2017 at 12:18 PM, Shamim wrote: > Good evening, Denis, > The direct URL of the post is as follows: > http://frommyworkshop.blogspot.ru/2016/09/book-high- > performance-in-memory.html > > If I will have any new post, I will let

Re: Extend TcpDiscoveryVmIpFinder functionality

On Mon, Jan 9, 2017 at 12:19 PM, Sergey Kozlov wrote: > Hi > > Thanks Yakov and Vladimir! > > In general I'm ok for Yakov's suggestion though a bit not clear why > discovery by network mask will take long time. Is the discovery spi > single-threaded and Ignite processes the addresses consequentia

Hi guys /Artem Schitow/

Hi guys! I would like to join the development of Apache Ignite. I’m Artem Schitow, Russia. I did work with Ignite as a “user” at my previous job at e-commerce firm, and I’m interested in becoming more involved with the community as I find the project useful and unique in its own way. I would b

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

Roman's blog has been added to the website - https://ignite.apache.org/ blogs.html -Prachi On Mon, Jan 9, 2017 at 10:33 AM, Denis Magda wrote: > Roman, perfect! Well done! > > *Prachi*, please add Roman’s blog to Apache Ignite’s blogs list: > https://ignite.apache.org/blogs.html > > *Sally*,

Re: Contributing to Ignite.NET

Great, Sergey thanks! I’ve added you to the contributors list on Ignite’s main site. https://ignite.apache.org/community/resources.html#people Pavel, could you add a number of .NET related tickets to this “Pick a Ticket” section? https

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

Thanks, Denis. I'm working on a draft and will send it over for review in the next couple of days. Kind regards,Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] On Mon, Jan 9, 2017 at 13:33, Denis Magda wrote: Roman, perfect! Well done! *Prachi

Re: Adding blog posts to Apache Ignite's blogs list

Dimitriy, Glad to see you again. Thank'x a lot to purchase the book ( it was unnecessary, we can send you a gift copy of the book), we will be glad to hear from you any constructive criticisms and suggestions. With best regards Shamim Ahmed > On 9 янв. 2017 г., at 23:40, Dmitriy Setrakyan

Re: Hi guys /Artem Schitow/

Hi Artem, Welcome to the Ignite community! I’ve added you to the contributors list in JIRA. A piece of other relevant information that might be useful to you. Please subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite dev

SQL query collocated flag

Folks, One of the users faced an interesting case [1]. Basically, there is a query [2] which returns correct result when collocated flag is not set, but if it's true, several counts for each node is received by the client without being aggregated. Is this expected? I'm also attaching the test that

Re: Adding blog posts to Apache Ignite's blogs list

On Mon, Jan 9, 2017 at 1:18 PM, Shamim wrote: > Dimitriy, > Glad to see you again. Thank'x a lot to purchase the book ( it was > unnecessary, we can send you a gift copy of the book), we will be glad to > hear from you any constructive criticisms and suggestions. > You did great work, I was ha

[GitHub] ignite pull request #1411: IGNITE-2422: Prevent serialization of BinaryObjec...

GitHub user dream-x opened a pull request: https://github.com/apache/ignite/pull/1411 IGNITE-2422: Prevent serialization of BinaryObjectBuilder You can merge this pull request into a Git repository by running: $ git pull https://github.com/dream-x/ignite ignite-2422 Alternati

classnames.properties file is not updated and missed in 1.8 release

Committers, especially Anton V. and Vovan, I’ve been looking at the following ticket [1] and found out that the issue happens simply because both org.apache.ignite.binary.BinaryObjectBuilder and org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl are not added to META-INF/class

Re: classnames.properties file is not updated and missed in 1.8 release

I'm not sure about sources. But "mvn clean package" should generate "modules/core/target/classes/META-INF/classnames.properties" And yes, I think we should also push "fresh" classnames.properties as one of pre-release steps. On Tue, Jan 10, 2017 at 7:51 AM, Denis Magda wrote: > Committers, esp

Integration with RocketMQ

Igniters, Recently I am looking into a new pub/sub messaging Apache incubator project called RocketMQ [1], originally developed at Alibaba. And I am thinking about implementing a streamer for Ignite. Do you think it has to be placed under modules/ of Ignite project, or better to have it together