[GitHub] ignite pull request #2241: IGNITE-5695 FlinkIgniteSinkSelfTest is failing du...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2241


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: usage analytics

[Rishi Yagnik]

With such statistics collected by Ignite , we won't ever accept ignite in our 
environment.

However, turning on and off stats collection capabilities would be helpful here 
if the feature is accepted further for implementation.

Take Care,
Rishi

> On Jul 5, 2017, at 8:15 PM, Roman Shtykh  wrote:
> 
> NIkita,
> 
> While this will help improve Ignite, it will prevent its adoption by many 
> projects -- sending and retaining IP adresses, OS versions, etc. raises tons 
> of questions when considering to use Ignite. Even if it can be opted out.
> -- Roman
> 
> 
>On Thursday, July 6, 2017 5:38 AM, Nikita Ivanov  
> wrote:
> 
> 
> Igniters,
> I would like to kick off the discussion on the idea of collecting Ignite
> usage statistics. The basic idea behind this is to better understand
> general and anonymous Ignite usage information to better calibrate
> community efforts in developing new features, improving existing ones,
> delivering better documentation - and in every other way to make our
> project a better software solution.
> 
> Although such instrumentation is standard practice in commercially
> developed software, for an ASF project this could be a sensitive issue.
> Therefore I would like to initiate a full community discussion on how best
> to implement such practice for the benefit of project while ensuring the
> privacy protection of Ignite users.
> 
> To ignite (pun intended) the discussion I'll outline below some of the
> basic thoughts that I have on this subject. They are here only to give an
> idea of what such instrumentation may potentially look like so that we can
> discuss the merits of this idea in a tangible context.
> 
> Overview
> -
> Upon start and every hour thereafter each Ignite node will collect, encrypt
> and send usage statistics over HTTPS to the ASF-hosted server. That server
> will accept such HTTPS packets, decrypt them and store them in a
> time-series DB. A web interface will be provided to view the usage
> information.
> 
> Opt-In or Opt-out
> -
> Opt-out. Ignite website will offer simple instructions (system property) on
> how to disable this instrumentation.
> 
> Code, Infra, Access
> ---
> Ignite instrumentation will be part of the Ignite code base. The collection
> server will be a separate module in the Ignite code base (released
> separately from Ignite). The collection server will be hosted by ASF Infra.
> 
> Usage statistics will be publicly accessible by anyone in the community.
> 
> Private, Personal Data
> --
> No private or personal data will ever be transferred. No emails, usernames,
> company names, grid names, etc.
> 
> Data Retention
> 
> All data will be retained for 1 year and deleted permanently thereafter.
> 
> Usage Data
> 
> The following data will be collected in each packet sent to the collection
> server:
> - GRID_SIZE (to correspond our testing environment with the more frequent
> cluster sizes)
> - IP_ADDR (for general geo-tracking as well as to know what documentation
> language should be a priority)
> - SES_ID (to track continues uptime vs. re-starts)
> - USERNAME_TYPE (privilege username vs. standard, to track production vs.
> dev/testing usage; note - this is not an actual username)
> - OS_NAME
> - OS_VER
> - OS_ARCH
> - JAVA_VER
> - JAVA_VENDOR
> - COMP_SQL (whether or not this feature was used)
> - COMP_COMPUTE (whether or not this feature was used)
> - COMP_DATAGRID (whether or not this feature was used)
> - COMP_STREAMING (whether or not this feature was used)
> - COMP_IGFS (whether or not this feature was used)
> - COMP_SERVICE (whether or not this feature was used)
> - COMP_PERSISTENCE (whether or not this feature was used)
> 
> Please let's discuss this idea. Everyone's comments and suggestions are
> *extremely* welcome.
> 
> Thanks,
> Nikita Ivanov.
> 
> 

Re: usage analytics

[Nikita Ivanov]

Roman,
Thanks for the feedback. What are those questions specifically? Are IP
addresses and OS is what causing it?

Thanks!

--
Nikita Ivanov
Founder & CTO
GridGain Systems

On Wed, Jul 5, 2017 at 6:15 PM, Roman Shtykh 
wrote:

> NIkita,
>
> While this will help improve Ignite, it will prevent its adoption by many
> projects -- sending and retaining IP adresses, OS versions, etc. raises
> tons of questions when considering to use Ignite. Even if it can be opted
> out.
> -- Roman
>
>
> On Thursday, July 6, 2017 5:38 AM, Nikita Ivanov 
> wrote:
>
>
>  Igniters,
> I would like to kick off the discussion on the idea of collecting Ignite
> usage statistics. The basic idea behind this is to better understand
> general and anonymous Ignite usage information to better calibrate
> community efforts in developing new features, improving existing ones,
> delivering better documentation - and in every other way to make our
> project a better software solution.
>
> Although such instrumentation is standard practice in commercially
> developed software, for an ASF project this could be a sensitive issue.
> Therefore I would like to initiate a full community discussion on how best
> to implement such practice for the benefit of project while ensuring the
> privacy protection of Ignite users.
>
> To ignite (pun intended) the discussion I'll outline below some of the
> basic thoughts that I have on this subject. They are here only to give an
> idea of what such instrumentation may potentially look like so that we can
> discuss the merits of this idea in a tangible context.
>
> Overview
> -
> Upon start and every hour thereafter each Ignite node will collect, encrypt
> and send usage statistics over HTTPS to the ASF-hosted server. That server
> will accept such HTTPS packets, decrypt them and store them in a
> time-series DB. A web interface will be provided to view the usage
> information.
>
> Opt-In or Opt-out
> -
> Opt-out. Ignite website will offer simple instructions (system property) on
> how to disable this instrumentation.
>
> Code, Infra, Access
> ---
> Ignite instrumentation will be part of the Ignite code base. The collection
> server will be a separate module in the Ignite code base (released
> separately from Ignite). The collection server will be hosted by ASF Infra.
>
> Usage statistics will be publicly accessible by anyone in the community.
>
> Private, Personal Data
> --
> No private or personal data will ever be transferred. No emails, usernames,
> company names, grid names, etc.
>
> Data Retention
> 
> All data will be retained for 1 year and deleted permanently thereafter.
>
> Usage Data
> 
> The following data will be collected in each packet sent to the collection
> server:
> - GRID_SIZE (to correspond our testing environment with the more frequent
> cluster sizes)
> - IP_ADDR (for general geo-tracking as well as to know what documentation
> language should be a priority)
> - SES_ID (to track continues uptime vs. re-starts)
> - USERNAME_TYPE (privilege username vs. standard, to track production vs.
> dev/testing usage; note - this is not an actual username)
> - OS_NAME
> - OS_VER
> - OS_ARCH
> - JAVA_VER
> - JAVA_VENDOR
> - COMP_SQL (whether or not this feature was used)
> - COMP_COMPUTE (whether or not this feature was used)
> - COMP_DATAGRID (whether or not this feature was used)
> - COMP_STREAMING (whether or not this feature was used)
> - COMP_IGFS (whether or not this feature was used)
> - COMP_SERVICE (whether or not this feature was used)
> - COMP_PERSISTENCE (whether or not this feature was used)
>
> Please let's discuss this idea. Everyone's comments and suggestions are
> *extremely* welcome.
>
> Thanks,
> Nikita Ivanov.
>
>
>

(IGNITE-5695) FlinkIgniteSinkSelfTest is failing due to conflicting default test timeout and default flush frequency

[Saikat Maitra]

Hi,

I have raised a PR to address the failing test FlinkIgniteSinkSelfTest due
to same timeout settings for test and data flush frequency.

Please review and let me know feedback.

jira - https://issues.apache.org/jira/browse/IGNITE-5695
PR - https://github.com/apache/ignite/pull/2241

Regards,
Saikat

Re: Apache Ignite 2.1 scope

[Konstantin Boudnik]

Thanks everyone for giving us enough time to take a look into the code
and architecture of this new feature. The webinar was certainly quite
helpful (thanks Denis!).

It seems to be a good time to add the feature into the dot-release, so
more users can have a taste of it "officially". I have a somewhat
unrelated question though: it seems that 2.0 has significant
performance degradation compared to 1.8 when it get to the working
with external distributed storage (like Cassandra). Could it be caused
by all the changes that were made between 1.8 and 2.0 in the
preparation for the coming persistent store functionality? Are we
publishing/collecting say yardstick reports for our own releases?

Thanks!
  Cos
--
  Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.


On Tue, Jul 4, 2017 at 3:20 AM, Vladimir Ozerov  wrote:
> Igniters,
>
> Persistent store has been merged to master branch! "master-bak" branch was
> created to keep the state before merge for safety. As release date for 2.1
> is mid July, I created "ignite-2.1" branch where we will stabilize the
> release as usual. Please push features and fixes planned for 2.1 release to
> this branch. The rest commits should go to master.
>
> Vladimir.
>
> On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov 
> wrote:
>
>> Hi Denis,
>>
>> Awesome news! I'll take care of necessary release procedures if nobody
>> minds.
>>
>> Vladimir.
>>
>> On Sat, Jul 1, 2017 at 12:25 AM, Denis Magda  wrote:
>>
>>> 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, it’s absolutely fine to make it
>>> available in the nearest release.
>>>
>>> My proposal is to do the release by mid of July (closer to July 15th). Is
>>> there anyone who is ready to take over as a release manager creating the
>>> page like this [2] and handling all release related activities?
>>>
>>>
>>> [1] http://apache-ignite-developers.2346864.n4.nabble.com/
>>> Ignite-Persistent-Store-Ready-for-merge-td19160.html
>>> [2] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0
>>>
>>> —
>>> Denis
>>>
>>> > On Jun 1, 2017, at 9:24 AM, Alexander Paschenko <
>>> alexander.a.pasche...@gmail.com> wrote:
>>> >
>>> > IGNITE-5327 Create predefined cache templates for CREATE TABLE command
>>> > - minor comments left, ETA is Friday.
>>> >
>>> > IGNITE-5380 Validate cache QueryEntities in discovery thread - in
>>> > progress, the meat of code is written, but need to add lots of tests.
>>> > ETA is Friday.
>>> >
>>> > IGNITE-5188 Support AFFINITY KEY keyword for CREATE TABLE command - in
>>> > progress, made few first small steps, ETA is Friday.
>>> >
>>> > Rest is closed/patch available, ignite-4994 has been moved to 2.2.
>>> >
>>> > - Alex
>>> >
>>> > 2017-06-01 19:03 GMT+03:00 Sergey Chugunov :
>>> >>   1. IGNITE-5386 Inactive mode must be forced on starting up grid with
>>> >>   persistence is enabled
>>> >>   It is important improvement to fix critical bug IGNITE-5363.
>>> >>   Working on it, ETA - tomorrow.
>>> >>   2. IGNITE-5375 New PersistentStoreMetrics, MemoryMetrics interface
>>> >>   improvements
>>> >>   A lot of discussions were on this topic, ticket created only today
>>> and
>>> >>   requires several days to implement.
>>> >>
>>> >>
>>> >>
>>> >> On Thu, Jun 1, 2017 at 6:56 PM, Taras Ledkov 
>>> wrote:
>>> >>
>>> >>> Folks,
>>> >>>
>>> >>> IGNITE-4922 JDBC Driver: renew thin client based solution:
>>> >>>
>>> >>> On 2.1 the functionality of the new thin client JDBC driver will be
>>> >>> between deprecated Ignite thin JDBC and Ignite JDBCv2.
>>> >>> 1. The most functions of SQL query (include DML) are implemented and
>>> ready
>>> >>> for review;
>>> >>> 2. The most functions of JDBC metadata are implemented and ready for
>>> >>> review;
>>> >>> 3. Transactions, batching, streaming, blobs, scrollable / writable
>>> cursors
>>> >>> will not be supported in 2.1.
>>> >>>
>>> >>>
>>> >>>
>>> >>> On 01.06.2017 18:43, Vladimir Ozerov wrote:
>>> >>>
>>>  Folks,
>>> 
>>>  We are almost reached proposed feature-complete date (June 2), Could
>>> you
>>>  please share current status of your major features?
>>> 
>>>  On Tue, May 16, 2017 at 3:51 AM, Dmitriy Setrakyan <
>>> dsetrak...@apache.org
>>> >
>>>  wrote:
>>> 
>>>  Looks a little tight. Let's hope we can make it.
>>> >
>>> > On Mon, May 15, 2017 at 1:29 PM, Denis Magda 
>>> wrote:
>>> >
>>> 

Re: usage analytics

[Roman Shtykh]

NIkita,

While this will help improve Ignite, it will prevent its adoption by many 
projects -- sending and retaining IP adresses, OS versions, etc. raises tons of 
questions when considering to use Ignite. Even if it can be opted out.
-- Roman


On Thursday, July 6, 2017 5:38 AM, Nikita Ivanov  
wrote:
 

 Igniters,
I would like to kick off the discussion on the idea of collecting Ignite
usage statistics. The basic idea behind this is to better understand
general and anonymous Ignite usage information to better calibrate
community efforts in developing new features, improving existing ones,
delivering better documentation - and in every other way to make our
project a better software solution.

Although such instrumentation is standard practice in commercially
developed software, for an ASF project this could be a sensitive issue.
Therefore I would like to initiate a full community discussion on how best
to implement such practice for the benefit of project while ensuring the
privacy protection of Ignite users.

To ignite (pun intended) the discussion I'll outline below some of the
basic thoughts that I have on this subject. They are here only to give an
idea of what such instrumentation may potentially look like so that we can
discuss the merits of this idea in a tangible context.

Overview
-
Upon start and every hour thereafter each Ignite node will collect, encrypt
and send usage statistics over HTTPS to the ASF-hosted server. That server
will accept such HTTPS packets, decrypt them and store them in a
time-series DB. A web interface will be provided to view the usage
information.

Opt-In or Opt-out
-
Opt-out. Ignite website will offer simple instructions (system property) on
how to disable this instrumentation.

Code, Infra, Access
---
Ignite instrumentation will be part of the Ignite code base. The collection
server will be a separate module in the Ignite code base (released
separately from Ignite). The collection server will be hosted by ASF Infra.

Usage statistics will be publicly accessible by anyone in the community.

Private, Personal Data
--
No private or personal data will ever be transferred. No emails, usernames,
company names, grid names, etc.

Data Retention

All data will be retained for 1 year and deleted permanently thereafter.

Usage Data

The following data will be collected in each packet sent to the collection
server:
- GRID_SIZE (to correspond our testing environment with the more frequent
cluster sizes)
- IP_ADDR (for general geo-tracking as well as to know what documentation
language should be a priority)
- SES_ID (to track continues uptime vs. re-starts)
- USERNAME_TYPE (privilege username vs. standard, to track production vs.
dev/testing usage; note - this is not an actual username)
- OS_NAME
- OS_VER
- OS_ARCH
- JAVA_VER
- JAVA_VENDOR
- COMP_SQL (whether or not this feature was used)
- COMP_COMPUTE (whether or not this feature was used)
- COMP_DATAGRID (whether or not this feature was used)
- COMP_STREAMING (whether or not this feature was used)
- COMP_IGFS (whether or not this feature was used)
- COMP_SERVICE (whether or not this feature was used)
- COMP_PERSISTENCE (whether or not this feature was used)

Please let's discuss this idea. Everyone's comments and suggestions are
*extremely* welcome.

Thanks,
Nikita Ivanov.


   

Re: Distributed scheduling

[Konstantin Boudnik]

Seems like a simple API for an external cron-like service to invoke an
action in Ignite would suffice, no? There are about a million of
scheduling services like that already, some have very good integration
into orchestrators of all sorts. Perhaps a trivial REST would do
instead of durable services, etc.?

Cos
--
  Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.


On Mon, Jul 3, 2017 at 3:35 PM, Valentin Kulichenko
 wrote:
> Dmitry,
>
> Yes, this can be implemented using services in many cases, but:
>
> - It will require user to implement actual scheduling logic. It's quite a
> generic task, so I think it makes sense to have it directly on the API.
> - Most likely it will imply deploying separate service for each scheduled
> task. I don't think it's a very good idea.
> - Current services implementation is not durable. If cluster is restarted,
> all services are lost.
>
> -Val
>
> On Sat, Jul 1, 2017 at 12:34 AM, Dmitriy Setrakyan 
> wrote:
>
>> Val,
>>
>> In this case, we should have a notion of a named scheduler and ensure that
>> we don't schedule the same task more than once. This is beginning to look
>> more like a durable cluster singleton service, no?
>>
>> D.
>>
>> On Fri, Jun 30, 2017 at 1:39 PM, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>>
>> > 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 IgniteCompute#withSchedulingPolicy(SchedulingPolicy policy)
>> > method, where SchedulingPolicy is smth like this:
>> >
>> > public interface SchedulingPolicy {
>> > /**
>> >  * @return Timestamp of next execution.
>> >  */
>> > public Date nextTime();
>> > }
>> >
>> > This will enable scheduling for all compute features (tasks, callables,
>> > closures, etc.) and also very flexible. Policy implementation can provide
>> > simple periodic scheduling, scheduling based on Cron or anything else.
>> >
>> > Thoughts?
>> >
>> > -Val
>> >
>> > On Fri, Jun 30, 2017 at 7:55 AM, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>> > wrote:
>> >
>> > > On Fri, Jun 30, 2017 at 12:29 AM, Alexey Kuznetsov <
>> > akuznet...@apache.org>
>> > > 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();
>> > > >
>> > > > ignite.scheduler().schedulel(job, "0 0 * * *"); // This will execute
>> > job
>> > > > every day at 00:00
>> > > >
>> > > > 2) via compute
>> > > >
>> > > > Ignite ignite = Ignition.start();
>> > > >
>> > > > ignite.compute().schedulel(task, "0 0 * * *"); // This will execute
>> > > > compute
>> > > > task every day at 00:00
>> > > >
>> > > > Make sense?
>> > > >
>> > > >
>> > > Yes, it does, but I am failing to see how is this a *distributed*
>> > > scheduling. Are we persisting the scheduler somewhere in the cluster or
>> > is
>> > > it only triggered on the client side?
>> > >
>> >
>>

Re: abbrevation rules plugin

[Denis Magda]

Dmitriy P.,

Does it sound good to you? If yes, please make sure the plugin is available via 
a public GitHub repo and refer to it from the doc.

—
Denis

> On Jul 5, 2017, at 4:43 PM, Dmitriy Setrakyan  wrote:
> 
> On Wed, Jul 5, 2017 at 4:41 PM, Denis Magda  wrote:
> 
>> Ok, what if we make sure the plugin is available on GitHub (not Ignite)
>> and give a link to it on the documentation page? This seems to be the
>> easiest way to handle the topic.
> 
> 
> I think this will work.

Re: abbrevation rules plugin

[Dmitriy Setrakyan]

On Wed, Jul 5, 2017 at 4:41 PM, Denis Magda  wrote:

> Ok, what if we make sure the plugin is available on GitHub (not Ignite)
> and give a link to it on the documentation page? This seems to be the
> easiest way to handle the topic.


I think this will work.

Re: abbrevation rules plugin

[Denis Magda]

Ok, what if we make sure the plugin is available on GitHub (not Ignite) and 
give a link to it on the documentation page? This seems to be the easiest way 
to handle the topic.
 
—
Denis

> On Jul 5, 2017, at 4:37 PM, Dmitriy Setrakyan  wrote:
> 
> On Wed, Jul 5, 2017 at 4:35 PM, Denis Magda  wrote:
> 
>> Dmitriy,
>> 
>> I’m not suggesting to add the JAR to the source code or to any binary
>> package but rather treat it as a third party plugin developed by someone
>> for Ignite’s development simplification. It’s similar to the way the
>> community uses Intellij IDEA’s plugins or Team City or many other maven
>> modules imported in the project - they don’t need to be a part of Ignite
>> sources or binaries to be used.
>> 
> 
> In this case AI should not host the download itself, but provide a link for
> the plugin to be downloaded elsewhere. If AI hosts it and distributes it,
> then it needs to be built from the source code.
> 
> 
>> 
>> —
>> Denis
>> 
>>> On Jul 5, 2017, at 4:13 PM, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> Denis,
>>> 
>>> Apache cannot have any binary files anywhere in its code bases. All
>> binary
>>> JARs must be produced from a build process. If we are adding this plugin,
>>> then the source for it needs to be committed to AI code base and the JAR
>>> should be generated from the build.
>>> 
>>> Once the JAR is generated, only then you can include it on a web page to
>>> download.
>>> 
>>> D.
>>> 
>>> On Wed, Jul 5, 2017 at 3:19 PM, Denis Magda  wrote:
>>> 
 Guys,
 
 Let’s make things simple and attach the jar of the plugin to the wiki
>> page
 that refers to it:
 https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules <
 https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules>
 
 This should be fine from ASF standpoint.
 
 —
 Denis
 
> On Jul 5, 2017, at 9:58 AM, Dmitriy Setrakyan 
 wrote:
> 
> Hi Dmitriy,
> 
> The answer is No. We should put it as a source code and integrate it
>> into
> our build procedure.
> 
> D.
> 
> On Wed, Jul 5, 2017 at 9:46 AM, Dmitry Pavlov 
 wrote:
> 
>> Hi Igniters,
>> 
>> Could you please share your opinion about this topic?
>> 
>> The question is as follows: Is it allowed to place abbreviation plugin
 as
>> jar file into ignite source code? Abbrev-plugin.jar is jar file and I
>> am
>> not aware if it is allowed to place jars in git.
>> 
>> Sincerely,
>> Dmitriy Pavlov
>> 
>> 
>> ср, 5 июл. 2017 г. в 12:55, Dmitry Pavlov :
>> 
>>> Hi, I have created https://issues.apache.org/jira/browse/IGNITE-5698
 for
>>> this task.
>>> 
>>> It is not clear for me yet how to publish correctly - is it possible
>> to
>>> publish JAR.
>>> 
>>> ср, 5 июл. 2017 г. в 11:34, ALEKSEY KUZNETSOV <
 alkuznetsov...@gmail.com
>>> :
>>> 
 Yeah, it would be very helpful.
 
 вт, 4 июл. 2017 г. в 18:40, Dmitry Pavlov :
 
> Hi, Val,
> 
> No, this plugin is not available in apache-ignite code base.
> May be we should remove reference from JIRA or add this plugin (and
>> also
> other code inspections) into AI code base.
> Thoughts?
> 
> Sincerely,
> Dmitriy Pavlov
> 
> вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
> 
>> The plugin actually exists, not sure why it's not attached. Does
 anyone
> has
>> it?
>> 
>> -Val
>> 
>> On Mon, Jul 3, 2017 at 5:27 AM, ALEKSEY KUZNETSOV <
>> alkuznetsov...@gmail.com>
>> wrote:
>> 
>>> Igntrs!
>>> There is a plugin , mentioned  in Abbreviation Rules
>>> <
 https://cwiki.apache.org/confluence/display/IGNITE/
>> Abbreviation+Rules
>> 
>>> page
>>> that performs on-the-fly check.Is somebody going to add it some
>> day?
>>> --
>>> 
>>> *Best Regards,*
>>> 
>>> *Kuznetsov Aleksey*
>>> 
>> 
> 
 --
 
 *Best Regards,*
 
 *Kuznetsov Aleksey*
 
>>> 
>> 
 
 
>> 
>> 

Re: abbrevation rules plugin

[Dmitriy Setrakyan]

On Wed, Jul 5, 2017 at 4:35 PM, Denis Magda  wrote:

> Dmitriy,
>
> I’m not suggesting to add the JAR to the source code or to any binary
> package but rather treat it as a third party plugin developed by someone
> for Ignite’s development simplification. It’s similar to the way the
> community uses Intellij IDEA’s plugins or Team City or many other maven
> modules imported in the project - they don’t need to be a part of Ignite
> sources or binaries to be used.
>

In this case AI should not host the download itself, but provide a link for
the plugin to be downloaded elsewhere. If AI hosts it and distributes it,
then it needs to be built from the source code.


>
> —
> Denis
>
> > On Jul 5, 2017, at 4:13 PM, Dmitriy Setrakyan 
> wrote:
> >
> > Denis,
> >
> > Apache cannot have any binary files anywhere in its code bases. All
> binary
> > JARs must be produced from a build process. If we are adding this plugin,
> > then the source for it needs to be committed to AI code base and the JAR
> > should be generated from the build.
> >
> > Once the JAR is generated, only then you can include it on a web page to
> > download.
> >
> > D.
> >
> > On Wed, Jul 5, 2017 at 3:19 PM, Denis Magda  wrote:
> >
> >> Guys,
> >>
> >> Let’s make things simple and attach the jar of the plugin to the wiki
> page
> >> that refers to it:
> >> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules <
> >> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules>
> >>
> >> This should be fine from ASF standpoint.
> >>
> >> —
> >> Denis
> >>
> >>> On Jul 5, 2017, at 9:58 AM, Dmitriy Setrakyan 
> >> wrote:
> >>>
> >>> Hi Dmitriy,
> >>>
> >>> The answer is No. We should put it as a source code and integrate it
> into
> >>> our build procedure.
> >>>
> >>> D.
> >>>
> >>> On Wed, Jul 5, 2017 at 9:46 AM, Dmitry Pavlov 
> >> wrote:
> >>>
>  Hi Igniters,
> 
>  Could you please share your opinion about this topic?
> 
>  The question is as follows: Is it allowed to place abbreviation plugin
> >> as
>  jar file into ignite source code? Abbrev-plugin.jar is jar file and I
> am
>  not aware if it is allowed to place jars in git.
> 
>  Sincerely,
>  Dmitriy Pavlov
> 
> 
>  ср, 5 июл. 2017 г. в 12:55, Dmitry Pavlov :
> 
> > Hi, I have created https://issues.apache.org/jira/browse/IGNITE-5698
> >> for
> > this task.
> >
> > It is not clear for me yet how to publish correctly - is it possible
> to
> > publish JAR.
> >
> > ср, 5 июл. 2017 г. в 11:34, ALEKSEY KUZNETSOV <
> >> alkuznetsov...@gmail.com
> > :
> >
> >> Yeah, it would be very helpful.
> >>
> >> вт, 4 июл. 2017 г. в 18:40, Dmitry Pavlov :
> >>
> >>> Hi, Val,
> >>>
> >>> No, this plugin is not available in apache-ignite code base.
> >>> May be we should remove reference from JIRA or add this plugin (and
>  also
> >>> other code inspections) into AI code base.
> >>> Thoughts?
> >>>
> >>> Sincerely,
> >>> Dmitriy Pavlov
> >>>
> >>> вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
> >>> valentin.kuliche...@gmail.com>:
> >>>
>  The plugin actually exists, not sure why it's not attached. Does
> >> anyone
> >>> has
>  it?
> 
>  -Val
> 
>  On Mon, Jul 3, 2017 at 5:27 AM, ALEKSEY KUZNETSOV <
>  alkuznetsov...@gmail.com>
>  wrote:
> 
> > Igntrs!
> > There is a plugin , mentioned  in Abbreviation Rules
> > <
> >> https://cwiki.apache.org/confluence/display/IGNITE/
> Abbreviation+Rules
> 
> > page
> > that performs on-the-fly check.Is somebody going to add it some
>  day?
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
> >
> 
> >>>
> >> --
> >>
> >> *Best Regards,*
> >>
> >> *Kuznetsov Aleksey*
> >>
> >
> 
> >>
> >>
>
>

Re: abbrevation rules plugin

[Denis Magda]

Dmitriy,

I’m not suggesting to add the JAR to the source code or to any binary package 
but rather treat it as a third party plugin developed by someone for Ignite’s 
development simplification. It’s similar to the way the community uses Intellij 
IDEA’s plugins or Team City or many other maven modules imported in the project 
- they don’t need to be a part of Ignite sources or binaries to be used.

—
Denis

> On Jul 5, 2017, at 4:13 PM, Dmitriy Setrakyan  wrote:
> 
> Denis,
> 
> Apache cannot have any binary files anywhere in its code bases. All binary
> JARs must be produced from a build process. If we are adding this plugin,
> then the source for it needs to be committed to AI code base and the JAR
> should be generated from the build.
> 
> Once the JAR is generated, only then you can include it on a web page to
> download.
> 
> D.
> 
> On Wed, Jul 5, 2017 at 3:19 PM, Denis Magda  wrote:
> 
>> Guys,
>> 
>> Let’s make things simple and attach the jar of the plugin to the wiki page
>> that refers to it:
>> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules <
>> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules>
>> 
>> This should be fine from ASF standpoint.
>> 
>> —
>> Denis
>> 
>>> On Jul 5, 2017, at 9:58 AM, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> Hi Dmitriy,
>>> 
>>> The answer is No. We should put it as a source code and integrate it into
>>> our build procedure.
>>> 
>>> D.
>>> 
>>> On Wed, Jul 5, 2017 at 9:46 AM, Dmitry Pavlov 
>> wrote:
>>> 
 Hi Igniters,
 
 Could you please share your opinion about this topic?
 
 The question is as follows: Is it allowed to place abbreviation plugin
>> as
 jar file into ignite source code? Abbrev-plugin.jar is jar file and I am
 not aware if it is allowed to place jars in git.
 
 Sincerely,
 Dmitriy Pavlov
 
 
 ср, 5 июл. 2017 г. в 12:55, Dmitry Pavlov :
 
> Hi, I have created https://issues.apache.org/jira/browse/IGNITE-5698
>> for
> this task.
> 
> It is not clear for me yet how to publish correctly - is it possible to
> publish JAR.
> 
> ср, 5 июл. 2017 г. в 11:34, ALEKSEY KUZNETSOV <
>> alkuznetsov...@gmail.com
> :
> 
>> Yeah, it would be very helpful.
>> 
>> вт, 4 июл. 2017 г. в 18:40, Dmitry Pavlov :
>> 
>>> Hi, Val,
>>> 
>>> No, this plugin is not available in apache-ignite code base.
>>> May be we should remove reference from JIRA or add this plugin (and
 also
>>> other code inspections) into AI code base.
>>> Thoughts?
>>> 
>>> Sincerely,
>>> Dmitriy Pavlov
>>> 
>>> вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
>>> valentin.kuliche...@gmail.com>:
>>> 
 The plugin actually exists, not sure why it's not attached. Does
>> anyone
>>> has
 it?
 
 -Val
 
 On Mon, Jul 3, 2017 at 5:27 AM, ALEKSEY KUZNETSOV <
 alkuznetsov...@gmail.com>
 wrote:
 
> Igntrs!
> There is a plugin , mentioned  in Abbreviation Rules
> <
>> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules
 
> page
> that performs on-the-fly check.Is somebody going to add it some
 day?
> --
> 
> *Best Regards,*
> 
> *Kuznetsov Aleksey*
> 
 
>>> 
>> --
>> 
>> *Best Regards,*
>> 
>> *Kuznetsov Aleksey*
>> 
> 
 
>> 
>> 

Re: abbrevation rules plugin

[Dmitriy Setrakyan]

Denis,

Apache cannot have any binary files anywhere in its code bases. All binary
JARs must be produced from a build process. If we are adding this plugin,
then the source for it needs to be committed to AI code base and the JAR
should be generated from the build.

Once the JAR is generated, only then you can include it on a web page to
download.

D.

On Wed, Jul 5, 2017 at 3:19 PM, Denis Magda  wrote:

> Guys,
>
> Let’s make things simple and attach the jar of the plugin to the wiki page
> that refers to it:
> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules <
> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules>
>
> This should be fine from ASF standpoint.
>
> —
> Denis
>
> > On Jul 5, 2017, at 9:58 AM, Dmitriy Setrakyan 
> wrote:
> >
> > Hi Dmitriy,
> >
> > The answer is No. We should put it as a source code and integrate it into
> > our build procedure.
> >
> > D.
> >
> > On Wed, Jul 5, 2017 at 9:46 AM, Dmitry Pavlov 
> wrote:
> >
> >> Hi Igniters,
> >>
> >> Could you please share your opinion about this topic?
> >>
> >> The question is as follows: Is it allowed to place abbreviation plugin
> as
> >> jar file into ignite source code? Abbrev-plugin.jar is jar file and I am
> >> not aware if it is allowed to place jars in git.
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >>
> >> ср, 5 июл. 2017 г. в 12:55, Dmitry Pavlov :
> >>
> >>> Hi, I have created https://issues.apache.org/jira/browse/IGNITE-5698
> for
> >>> this task.
> >>>
> >>> It is not clear for me yet how to publish correctly - is it possible to
> >>> publish JAR.
> >>>
> >>> ср, 5 июл. 2017 г. в 11:34, ALEKSEY KUZNETSOV <
> alkuznetsov...@gmail.com
> >>> :
> >>>
>  Yeah, it would be very helpful.
> 
>  вт, 4 июл. 2017 г. в 18:40, Dmitry Pavlov :
> 
> > Hi, Val,
> >
> > No, this plugin is not available in apache-ignite code base.
> > May be we should remove reference from JIRA or add this plugin (and
> >> also
> > other code inspections) into AI code base.
> > Thoughts?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com>:
> >
> >> The plugin actually exists, not sure why it's not attached. Does
>  anyone
> > has
> >> it?
> >>
> >> -Val
> >>
> >> On Mon, Jul 3, 2017 at 5:27 AM, ALEKSEY KUZNETSOV <
> >> alkuznetsov...@gmail.com>
> >> wrote:
> >>
> >>> Igntrs!
> >>> There is a plugin , mentioned  in Abbreviation Rules
> >>> <
>  https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules
> >>
> >>> page
> >>> that performs on-the-fly check.Is somebody going to add it some
> >> day?
> >>> --
> >>>
> >>> *Best Regards,*
> >>>
> >>> *Kuznetsov Aleksey*
> >>>
> >>
> >
>  --
> 
>  *Best Regards,*
> 
>  *Kuznetsov Aleksey*
> 
> >>>
> >>
>
>

Re: It seems WebSession's removeAttribute does not support HttpSessionBindingListener

[Valentin Kulichenko]

Hi,

This fix seems to address only particular case when attribute is expired.
But this will not work in generic case, right? For example, if attribute is
put and removed explicitly, listener will not be invoked. I don't think we
should rely on underlying session here, the logic has to be properly
implemented in Ignite's session implementation.

BTW, if you're working on the ticket, please assign it to yourself and
follow the process. More details here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

-Val

On Wed, Jul 5, 2017 at 3:25 AM, yucigou  wrote:

> Ignite WebSessionV2 uses genuineSes as the original HttpSession.
>
> Therefore, when setting an attribute or setting the maxInactiveInterval,
> Ignite should tell the original HttpSession about it.
>
> Otherwise, when the web container (such as Tomcat) thinks that a session
> expires, or is invalidated, or a session attribute gets removed, etc.,
> session attributes' HttpSessionBindingListener's valueUnbound callback
> function will not get fired.
>
> So once the original HttpSession gets updated with the session attributes
> and the maxInactiveInterval, the web container will transitively trigger
> the
> session attributes' HttpSessionBindingListener's valueUnbound callback
> function when a session expires, etc.
>
> (By the way, tested with our app, and our issue is fixed:
> https://github.com/apache/ignite/pull/2243)
>
>
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/It-seems-WebSession-s-
> removeAttribute-does-not-support-HttpSessionBindingListener-
> tp19184p19480.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>

Re: abbrevation rules plugin

[Denis Magda]

Guys,

Let’s make things simple and attach the jar of the plugin to the wiki page that 
refers to it:
https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules 


This should be fine from ASF standpoint.

—
Denis

> On Jul 5, 2017, at 9:58 AM, Dmitriy Setrakyan  wrote:
> 
> Hi Dmitriy,
> 
> The answer is No. We should put it as a source code and integrate it into
> our build procedure.
> 
> D.
> 
> On Wed, Jul 5, 2017 at 9:46 AM, Dmitry Pavlov  wrote:
> 
>> Hi Igniters,
>> 
>> Could you please share your opinion about this topic?
>> 
>> The question is as follows: Is it allowed to place abbreviation plugin as
>> jar file into ignite source code? Abbrev-plugin.jar is jar file and I am
>> not aware if it is allowed to place jars in git.
>> 
>> Sincerely,
>> Dmitriy Pavlov
>> 
>> 
>> ср, 5 июл. 2017 г. в 12:55, Dmitry Pavlov :
>> 
>>> Hi, I have created https://issues.apache.org/jira/browse/IGNITE-5698 for
>>> this task.
>>> 
>>> It is not clear for me yet how to publish correctly - is it possible to
>>> publish JAR.
>>> 
>>> ср, 5 июл. 2017 г. в 11:34, ALEKSEY KUZNETSOV >> :
>>> 
 Yeah, it would be very helpful.
 
 вт, 4 июл. 2017 г. в 18:40, Dmitry Pavlov :
 
> Hi, Val,
> 
> No, this plugin is not available in apache-ignite code base.
> May be we should remove reference from JIRA or add this plugin (and
>> also
> other code inspections) into AI code base.
> Thoughts?
> 
> Sincerely,
> Dmitriy Pavlov
> 
> вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
> 
>> The plugin actually exists, not sure why it's not attached. Does
 anyone
> has
>> it?
>> 
>> -Val
>> 
>> On Mon, Jul 3, 2017 at 5:27 AM, ALEKSEY KUZNETSOV <
>> alkuznetsov...@gmail.com>
>> wrote:
>> 
>>> Igntrs!
>>> There is a plugin , mentioned  in Abbreviation Rules
>>> <
 https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules
>> 
>>> page
>>> that performs on-the-fly check.Is somebody going to add it some
>> day?
>>> --
>>> 
>>> *Best Regards,*
>>> 
>>> *Kuznetsov Aleksey*
>>> 
>> 
> 
 --
 
 *Best Regards,*
 
 *Kuznetsov Aleksey*
 
>>> 
>> 

usage analytics

[Nikita Ivanov]

Igniters,
I would like to kick off the discussion on the idea of collecting Ignite
usage statistics. The basic idea behind this is to better understand
general and anonymous Ignite usage information to better calibrate
community efforts in developing new features, improving existing ones,
delivering better documentation - and in every other way to make our
project a better software solution.

Although such instrumentation is standard practice in commercially
developed software, for an ASF project this could be a sensitive issue.
Therefore I would like to initiate a full community discussion on how best
to implement such practice for the benefit of project while ensuring the
privacy protection of Ignite users.

To ignite (pun intended) the discussion I'll outline below some of the
basic thoughts that I have on this subject. They are here only to give an
idea of what such instrumentation may potentially look like so that we can
discuss the merits of this idea in a tangible context.

Overview
-
Upon start and every hour thereafter each Ignite node will collect, encrypt
and send usage statistics over HTTPS to the ASF-hosted server. That server
will accept such HTTPS packets, decrypt them and store them in a
time-series DB. A web interface will be provided to view the usage
information.

Opt-In or Opt-out
-
Opt-out. Ignite website will offer simple instructions (system property) on
how to disable this instrumentation.

Code, Infra, Access
---
Ignite instrumentation will be part of the Ignite code base. The collection
server will be a separate module in the Ignite code base (released
separately from Ignite). The collection server will be hosted by ASF Infra.

Usage statistics will be publicly accessible by anyone in the community.

Private, Personal Data
--
No private or personal data will ever be transferred. No emails, usernames,
company names, grid names, etc.

Data Retention

All data will be retained for 1 year and deleted permanently thereafter.

Usage Data

The following data will be collected in each packet sent to the collection
server:
- GRID_SIZE (to correspond our testing environment with the more frequent
cluster sizes)
- IP_ADDR (for general geo-tracking as well as to know what documentation
language should be a priority)
- SES_ID (to track continues uptime vs. re-starts)
- USERNAME_TYPE (privilege username vs. standard, to track production vs.
dev/testing usage; note - this is not an actual username)
- OS_NAME
- OS_VER
- OS_ARCH
- JAVA_VER
- JAVA_VENDOR
- COMP_SQL (whether or not this feature was used)
- COMP_COMPUTE (whether or not this feature was used)
- COMP_DATAGRID (whether or not this feature was used)
- COMP_STREAMING (whether or not this feature was used)
- COMP_IGFS (whether or not this feature was used)
- COMP_SERVICE (whether or not this feature was used)
- COMP_PERSISTENCE (whether or not this feature was used)

Please let's discuss this idea. Everyone's comments and suggestions are
*extremely* welcome.

Thanks,
Nikita Ivanov.

[GitHub] ignite pull request #2249: Ignite-2.1.2

[agoncharuk]

GitHub user agoncharuk opened a pull request:

https://github.com/apache/ignite/pull/2249

Ignite-2.1.2



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2249.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2249


commit a5abdd579cc7ace5d17ebcc6555e3ce66c777917
Author: Vasiliy Sisko 
Date:   2017-07-04T11:44:42Z

ignite-2.1 Fixed minor issues and typos.

commit 6c9d2228d2aba6ba5be64bd20ef244e634aeaa5a
Author: Alexey Kuznetsov 
Date:   2017-07-04T12:30:46Z

ignite-2.1 Added persistent store metrics.

commit f39129020999561e9def300b9cc136138ea3698e
Author: Andrey V. Mashenkov 
Date:   2017-06-16T16:54:26Z

IGNITE-5527: Prevent starvation in stripe pool on unstable topology.

(cherry picked from commit 97ea507)

commit b69f53e0ccf9d3da42a99d4423fb3d8bdd60a7bb
Author: Pavel Tupitsyn 
Date:   2017-07-04T14:42:31Z

IGNITE-5629 .NET: CacheConfiguration copy constructor

commit 2e7adbfbbab62f3b98e0409d2f4ceabad89b4120
Author: agura 
Date:   2017-07-04T13:56:40Z

ignite-5685 JDBC prepared statement shouldn't clear parameters after 
execution

commit 9743fa3d711d0f1bbf0fa7ceec65237879f76d0d
Author: Ilya Lantukh 
Date:   2017-07-04T15:10:25Z

Muted hanging tests.

commit 114c42e14013fe5b7bd6f186f7db59a533d61f68
Author: Alexey Goncharuk 
Date:   2017-07-04T16:35:06Z

Cosmetic changes

commit 77c5dc7455b9bf020dee549cc91286a897dbfdbc
Author: Dmitriy Govorukhin 
Date:   2017-07-04T16:40:21Z

Added onCacheGroupStopped callback

commit ee7566b1063de69ca4f261ee2088d69d231b1c2a
Author: Dmitriy Govorukhin 
Date:   2017-07-04T17:00:09Z

Minor code cleanup

commit 44f3fac27bec89b5e70e87564c527e48565ddd2a
Author: dpavlov 
Date:   2017-07-04T17:23:40Z

IGNITE-5558 - Added ability to read WAL in standalone mode - Fixes #2174.

Signed-off-by: Alexey Goncharuk 

commit 90b67fa1b72b096943499e26e402988840bdbe97
Author: Sergey Chugunov 
Date:   2017-07-04T17:47:09Z

IGNITE-4536 two tests unmuted, one test removed as obsolete (IGNITE-5592) - 
Fixes #2235.

Signed-off-by: Alexey Goncharuk 

commit 50bb0901255707dc9601159803363a36aeafecab
Author: Ilya Lantukh 
Date:   2017-07-04T15:10:25Z

Muted hanging tests.

commit 5b7165ca717de038249570c4213f050ba9b5aee7
Author: Ilya Lantukh 
Date:   2017-07-04T17:57:56Z

IGNITE-5693 - Fixed semaphore flaky test - Fixes #2239.

Signed-off-by: Alexey Goncharuk 

commit 54572c3023dc03a55621fbb4754888b081791e31
Author: tledkov-gridgain 
Date:   2017-07-05T07:30:48Z

IGNITE-5340: Improved IgniteCacheAbstractQuerySelfTest to better test 
non-standard index names. This closes #2206.

commit 44fad244aa40f552159af153fefdf25d47c7375e
Author: tledkov-gridgain 
Date:   2017-07-05T08:18:48Z

IGNITE-5426: JdbcThinConnection.readOnly state propagation. This closes 
#2200.

commit 1337901f04c866e20093b20449c0872f089fb64b
Author: sboikov 
Date:   2017-07-05T08:19:43Z

Reworked cluster activation/deactivation.

commit b67b8c4438f240038b61ca65b947394106b0e43b
Author: sboikov 
Date:   2017-07-05T08:20:54Z

Merge remote-tracking branch 'origin/ignite-2.1' into ignite-2.1

commit f9f13cf083b481f004531710ec3835afdf5b7cef
Author: Pavel Tupitsyn 
Date:   2017-07-05T09:59:43Z

IGNITE-5605 .NET: Inject resources into remote event filters

commit aa21a9b59ec0266b4fee16e02d2796e6e0d1a9b5
Author: devozerov 
Date:   2017-07-05T11:18:32Z

Merge branch 'ignite-2.1' into ignite-2.1.2

commit 301f310b6348b3f6fbe54b16d065569755e71bce
Author: Igor Sapego 
Date:   2017-07-04T16:42:33Z

IGNITE-5663: ODBC: Closing cursor do not reset prepared statement anymore

(cherry picked from commit 64c156e)

commit 58a937e5310c62ccb557d8da959bc4ffa8bcca62
Author: sboikov 
Date:   2017-07-05T11:24:51Z

Diagnostic info for GridDhtTxFinishFuture.

commit 0f9a895a04cd4a4f6be8e006fc2afd6f720b2215
Author: sboikov 
Date:   2017-07-05T11:25:16Z

Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2

commit 15da654a3e5c2bbf14947f0d3dd08270a9ba6766
Author: Alexander Paschenko 

[GitHub] ignite pull request #2187: IGNITE-5576: Added Compute::Run() for C++

[isapego]

Github user isapego closed the pull request at:

https://github.com/apache/ignite/pull/2187


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: abbrevation rules plugin

[Dmitriy Setrakyan]

Hi Dmitriy,

The answer is No. We should put it as a source code and integrate it into
our build procedure.

D.

On Wed, Jul 5, 2017 at 9:46 AM, Dmitry Pavlov  wrote:

> Hi Igniters,
>
> Could you please share your opinion about this topic?
>
> The question is as follows: Is it allowed to place abbreviation plugin as
> jar file into ignite source code? Abbrev-plugin.jar is jar file and I am
> not aware if it is allowed to place jars in git.
>
> Sincerely,
> Dmitriy Pavlov
>
>
> ср, 5 июл. 2017 г. в 12:55, Dmitry Pavlov :
>
> > Hi, I have created https://issues.apache.org/jira/browse/IGNITE-5698 for
> > this task.
> >
> > It is not clear for me yet how to publish correctly - is it possible to
> > publish JAR.
> >
> > ср, 5 июл. 2017 г. в 11:34, ALEKSEY KUZNETSOV  >:
> >
> >> Yeah, it would be very helpful.
> >>
> >> вт, 4 июл. 2017 г. в 18:40, Dmitry Pavlov :
> >>
> >> > Hi, Val,
> >> >
> >> > No, this plugin is not available in apache-ignite code base.
> >> > May be we should remove reference from JIRA or add this plugin (and
> also
> >> > other code inspections) into AI code base.
> >> > Thoughts?
> >> >
> >> > Sincerely,
> >> > Dmitriy Pavlov
> >> >
> >> > вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
> >> > valentin.kuliche...@gmail.com>:
> >> >
> >> > > The plugin actually exists, not sure why it's not attached. Does
> >> anyone
> >> > has
> >> > > it?
> >> > >
> >> > > -Val
> >> > >
> >> > > On Mon, Jul 3, 2017 at 5:27 AM, ALEKSEY KUZNETSOV <
> >> > > alkuznetsov...@gmail.com>
> >> > > wrote:
> >> > >
> >> > > > Igntrs!
> >> > > > There is a plugin , mentioned  in Abbreviation Rules
> >> > > > <
> >> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules
> >> > >
> >> > > > page
> >> > > > that performs on-the-fly check.Is somebody going to add it some
> day?
> >> > > > --
> >> > > >
> >> > > > *Best Regards,*
> >> > > >
> >> > > > *Kuznetsov Aleksey*
> >> > > >
> >> > >
> >> >
> >> --
> >>
> >> *Best Regards,*
> >>
> >> *Kuznetsov Aleksey*
> >>
> >
>

Re: Apache Ignite 2.1 scope

[Denis Magda]

Yes, I think so.

—
Denis

> On Jul 5, 2017, at 7:48 AM, Vyacheslav Daradur  wrote:
> 
> Hi Igniters!
> 
> When code freeze of v.2.1 is planned?
> 
>>> tickets which will not be ready by the end of the week to the next
> release.
> 7 July?
> 
> 2017-07-04 18:39 GMT+03:00 Vladimir Ozerov :
> 
>> Igniters,
>> 
>> We have 536 tickets assinged to 2.1 release [1]. I propose to move all the
>> tickets which will not be ready by the end of the week to the next release.
>> You may use this report [2], which will show all the issues which are
>> either reported by you or assigned to you (you must be logged in to JIRA to
>> get correct results).
>> 
>> [1]
>> https://issues.apache.org/jira/issues/?jql=project%20%
>> 3D%20IGNITE%20AND%20status%20not%20in%20(Resolved%2C%
>> 20Closed)%20AND%20fixVersion%20%3D%202.1
>> [2]
>> https://issues.apache.org/jira/issues/?jql=project%20%
>> 3D%20IGNITE%20AND%20status%20not%20in%20(Resolved%2C%
>> 20Closed)%20AND%20fixVersion%20%3D%202.1%20AND%20(assignee%
>> 20%3D%20currentUser()%20or%20reporter%20%3D%20currentUser())
>> 
>> On Tue, Jul 4, 2017 at 1:20 PM, Vladimir Ozerov 
>> wrote:
>> 
>>> Igniters,
>>> 
>>> Persistent store has been merged to master branch! "master-bak" branch
>> was
>>> created to keep the state before merge for safety. As release date for
>> 2.1
>>> is mid July, I created "ignite-2.1" branch where we will stabilize the
>>> release as usual. Please push features and fixes planned for 2.1 release
>> to
>>> this branch. The rest commits should go to master.
>>> 
>>> Vladimir.
>>> 
>>> On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov 
>>> wrote:
>>> 
 Hi Denis,
 
 Awesome news! I'll take care of necessary release procedures if nobody
 minds.
 
 Vladimir.
 
 On Sat, Jul 1, 2017 at 12:25 AM, Denis Magda  wrote:
 
> 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, it’s absolutely fine to make it
> available in the nearest release.
> 
> My proposal is to do the release by mid of July (closer to July 15th).
> Is there anyone who is ready to take over as a release manager
>> creating the
> page like this [2] and handling all release related activities?
> 
> 
> [1] http://apache-ignite-developers.2346864.n4.nabble.com/Ignite
> -Persistent-Store-Ready-for-merge-td19160.html
> [2] https://cwiki.apache.org/confluence/display/IGNITE/
>> Apache+Ignite+2.0
> 
> —
> Denis
> 
>> On Jun 1, 2017, at 9:24 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>> 
>> IGNITE-5327 Create predefined cache templates for CREATE TABLE
>> command
>> - minor comments left, ETA is Friday.
>> 
>> IGNITE-5380 Validate cache QueryEntities in discovery thread - in
>> progress, the meat of code is written, but need to add lots of tests.
>> ETA is Friday.
>> 
>> IGNITE-5188 Support AFFINITY KEY keyword for CREATE TABLE command -
>> in
>> progress, made few first small steps, ETA is Friday.
>> 
>> Rest is closed/patch available, ignite-4994 has been moved to 2.2.
>> 
>> - Alex
>> 
>> 2017-06-01 19:03 GMT+03:00 Sergey Chugunov <
>> sergey.chugu...@gmail.com
>> :
>>>  1. IGNITE-5386 Inactive mode must be forced on starting up grid
>> with
>>>  persistence is enabled
>>>  It is important improvement to fix critical bug IGNITE-5363.
>>>  Working on it, ETA - tomorrow.
>>>  2. IGNITE-5375 New PersistentStoreMetrics, MemoryMetrics interface
>>>  improvements
>>>  A lot of discussions were on this topic, ticket created only today
> and
>>>  requires several days to implement.
>>> 
>>> 
>>> 
>>> On Thu, Jun 1, 2017 at 6:56 PM, Taras Ledkov 
> wrote:
>>> 
 Folks,
 
 IGNITE-4922 JDBC Driver: renew thin client based solution:
 
 On 2.1 the functionality of the new thin client JDBC driver will be
 between deprecated Ignite thin JDBC and Ignite JDBCv2.
 1. The most functions of SQL query (include DML) are implemented
>> and
> ready
 for review;
 2. The most functions of JDBC metadata are implemented and ready
>> for
 review;
 3. Transactions, batching, streaming, blobs, scrollable / writable
> cursors
 will not be supported in 2.1.
 
 
 
 On 01.06.2017 18:43, Vladimir Ozerov wrote:
 
> Folks,
> 
> We are almost reached proposed feature-complete date (June 2),
> Could you
> please 

[GitHub] ignite pull request #2248: IGNITE-5483: SQL: Added limited support for Java8...

[skalashnikov]

GitHub user skalashnikov opened a pull request:

https://github.com/apache/ignite/pull/2248

IGNITE-5483: SQL: Added limited support for Java8 LocalDateTime



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5483

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2248.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2248


commit a5abdd579cc7ace5d17ebcc6555e3ce66c777917
Author: Vasiliy Sisko 
Date:   2017-07-04T11:44:42Z

ignite-2.1 Fixed minor issues and typos.

commit 6c9d2228d2aba6ba5be64bd20ef244e634aeaa5a
Author: Alexey Kuznetsov 
Date:   2017-07-04T12:30:46Z

ignite-2.1 Added persistent store metrics.

commit f39129020999561e9def300b9cc136138ea3698e
Author: Andrey V. Mashenkov 
Date:   2017-06-16T16:54:26Z

IGNITE-5527: Prevent starvation in stripe pool on unstable topology.

(cherry picked from commit 97ea507)

commit b69f53e0ccf9d3da42a99d4423fb3d8bdd60a7bb
Author: Pavel Tupitsyn 
Date:   2017-07-04T14:42:31Z

IGNITE-5629 .NET: CacheConfiguration copy constructor

commit 2e7adbfbbab62f3b98e0409d2f4ceabad89b4120
Author: agura 
Date:   2017-07-04T13:56:40Z

ignite-5685 JDBC prepared statement shouldn't clear parameters after 
execution

commit 9743fa3d711d0f1bbf0fa7ceec65237879f76d0d
Author: Ilya Lantukh 
Date:   2017-07-04T15:10:25Z

Muted hanging tests.

commit 114c42e14013fe5b7bd6f186f7db59a533d61f68
Author: Alexey Goncharuk 
Date:   2017-07-04T16:35:06Z

Cosmetic changes

commit 77c5dc7455b9bf020dee549cc91286a897dbfdbc
Author: Dmitriy Govorukhin 
Date:   2017-07-04T16:40:21Z

Added onCacheGroupStopped callback

commit ee7566b1063de69ca4f261ee2088d69d231b1c2a
Author: Dmitriy Govorukhin 
Date:   2017-07-04T17:00:09Z

Minor code cleanup

commit 44f3fac27bec89b5e70e87564c527e48565ddd2a
Author: dpavlov 
Date:   2017-07-04T17:23:40Z

IGNITE-5558 - Added ability to read WAL in standalone mode - Fixes #2174.

Signed-off-by: Alexey Goncharuk 

commit 90b67fa1b72b096943499e26e402988840bdbe97
Author: Sergey Chugunov 
Date:   2017-07-04T17:47:09Z

IGNITE-4536 two tests unmuted, one test removed as obsolete (IGNITE-5592) - 
Fixes #2235.

Signed-off-by: Alexey Goncharuk 

commit 50bb0901255707dc9601159803363a36aeafecab
Author: Ilya Lantukh 
Date:   2017-07-04T15:10:25Z

Muted hanging tests.

commit 5b7165ca717de038249570c4213f050ba9b5aee7
Author: Ilya Lantukh 
Date:   2017-07-04T17:57:56Z

IGNITE-5693 - Fixed semaphore flaky test - Fixes #2239.

Signed-off-by: Alexey Goncharuk 

commit 54572c3023dc03a55621fbb4754888b081791e31
Author: tledkov-gridgain 
Date:   2017-07-05T07:30:48Z

IGNITE-5340: Improved IgniteCacheAbstractQuerySelfTest to better test 
non-standard index names. This closes #2206.

commit 44fad244aa40f552159af153fefdf25d47c7375e
Author: tledkov-gridgain 
Date:   2017-07-05T08:18:48Z

IGNITE-5426: JdbcThinConnection.readOnly state propagation. This closes 
#2200.

commit 1337901f04c866e20093b20449c0872f089fb64b
Author: sboikov 
Date:   2017-07-05T08:19:43Z

Reworked cluster activation/deactivation.

commit b67b8c4438f240038b61ca65b947394106b0e43b
Author: sboikov 
Date:   2017-07-05T08:20:54Z

Merge remote-tracking branch 'origin/ignite-2.1' into ignite-2.1

commit f9f13cf083b481f004531710ec3835afdf5b7cef
Author: Pavel Tupitsyn 
Date:   2017-07-05T09:59:43Z

IGNITE-5605 .NET: Inject resources into remote event filters

commit aa21a9b59ec0266b4fee16e02d2796e6e0d1a9b5
Author: devozerov 
Date:   2017-07-05T11:18:32Z

Merge branch 'ignite-2.1' into ignite-2.1.2

commit 301f310b6348b3f6fbe54b16d065569755e71bce
Author: Igor Sapego 
Date:   2017-07-04T16:42:33Z

IGNITE-5663: ODBC: Closing cursor do not reset prepared statement anymore

(cherry picked from commit 64c156e)

commit 58a937e5310c62ccb557d8da959bc4ffa8bcca62
Author: sboikov 
Date:   2017-07-05T11:24:51Z

Diagnostic info for GridDhtTxFinishFuture.

commit 0f9a895a04cd4a4f6be8e006fc2afd6f720b2215
Author: sboikov 
Date:   2017-07-05T11:25:16Z

Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2

commit 15da654a3e5c2bbf14947f0d3dd08270a9ba6766
Author: 

[GitHub] ignite pull request #2247: IGNITE-5441 .NET: Propagate CacheStore exception ...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/2247

IGNITE-5441 .NET: Propagate CacheStore exception stack traces to the caller 
node



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-5441

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2247.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2247


commit a5abdd579cc7ace5d17ebcc6555e3ce66c777917
Author: Vasiliy Sisko 
Date:   2017-07-04T11:44:42Z

ignite-2.1 Fixed minor issues and typos.

commit 6c9d2228d2aba6ba5be64bd20ef244e634aeaa5a
Author: Alexey Kuznetsov 
Date:   2017-07-04T12:30:46Z

ignite-2.1 Added persistent store metrics.

commit f39129020999561e9def300b9cc136138ea3698e
Author: Andrey V. Mashenkov 
Date:   2017-06-16T16:54:26Z

IGNITE-5527: Prevent starvation in stripe pool on unstable topology.

(cherry picked from commit 97ea507)

commit b69f53e0ccf9d3da42a99d4423fb3d8bdd60a7bb
Author: Pavel Tupitsyn 
Date:   2017-07-04T14:42:31Z

IGNITE-5629 .NET: CacheConfiguration copy constructor

commit 2e7adbfbbab62f3b98e0409d2f4ceabad89b4120
Author: agura 
Date:   2017-07-04T13:56:40Z

ignite-5685 JDBC prepared statement shouldn't clear parameters after 
execution

commit 9743fa3d711d0f1bbf0fa7ceec65237879f76d0d
Author: Ilya Lantukh 
Date:   2017-07-04T15:10:25Z

Muted hanging tests.

commit 114c42e14013fe5b7bd6f186f7db59a533d61f68
Author: Alexey Goncharuk 
Date:   2017-07-04T16:35:06Z

Cosmetic changes

commit 77c5dc7455b9bf020dee549cc91286a897dbfdbc
Author: Dmitriy Govorukhin 
Date:   2017-07-04T16:40:21Z

Added onCacheGroupStopped callback

commit ee7566b1063de69ca4f261ee2088d69d231b1c2a
Author: Dmitriy Govorukhin 
Date:   2017-07-04T17:00:09Z

Minor code cleanup

commit 44f3fac27bec89b5e70e87564c527e48565ddd2a
Author: dpavlov 
Date:   2017-07-04T17:23:40Z

IGNITE-5558 - Added ability to read WAL in standalone mode - Fixes #2174.

Signed-off-by: Alexey Goncharuk 

commit 90b67fa1b72b096943499e26e402988840bdbe97
Author: Sergey Chugunov 
Date:   2017-07-04T17:47:09Z

IGNITE-4536 two tests unmuted, one test removed as obsolete (IGNITE-5592) - 
Fixes #2235.

Signed-off-by: Alexey Goncharuk 

commit 50bb0901255707dc9601159803363a36aeafecab
Author: Ilya Lantukh 
Date:   2017-07-04T15:10:25Z

Muted hanging tests.

commit 5b7165ca717de038249570c4213f050ba9b5aee7
Author: Ilya Lantukh 
Date:   2017-07-04T17:57:56Z

IGNITE-5693 - Fixed semaphore flaky test - Fixes #2239.

Signed-off-by: Alexey Goncharuk 

commit 54572c3023dc03a55621fbb4754888b081791e31
Author: tledkov-gridgain 
Date:   2017-07-05T07:30:48Z

IGNITE-5340: Improved IgniteCacheAbstractQuerySelfTest to better test 
non-standard index names. This closes #2206.

commit 44fad244aa40f552159af153fefdf25d47c7375e
Author: tledkov-gridgain 
Date:   2017-07-05T08:18:48Z

IGNITE-5426: JdbcThinConnection.readOnly state propagation. This closes 
#2200.

commit 1337901f04c866e20093b20449c0872f089fb64b
Author: sboikov 
Date:   2017-07-05T08:19:43Z

Reworked cluster activation/deactivation.

commit b67b8c4438f240038b61ca65b947394106b0e43b
Author: sboikov 
Date:   2017-07-05T08:20:54Z

Merge remote-tracking branch 'origin/ignite-2.1' into ignite-2.1

commit f9f13cf083b481f004531710ec3835afdf5b7cef
Author: Pavel Tupitsyn 
Date:   2017-07-05T09:59:43Z

IGNITE-5605 .NET: Inject resources into remote event filters

commit aa21a9b59ec0266b4fee16e02d2796e6e0d1a9b5
Author: devozerov 
Date:   2017-07-05T11:18:32Z

Merge branch 'ignite-2.1' into ignite-2.1.2

commit 301f310b6348b3f6fbe54b16d065569755e71bce
Author: Igor Sapego 
Date:   2017-07-04T16:42:33Z

IGNITE-5663: ODBC: Closing cursor do not reset prepared statement anymore

(cherry picked from commit 64c156e)

commit 58a937e5310c62ccb557d8da959bc4ffa8bcca62
Author: sboikov 
Date:   2017-07-05T11:24:51Z

Diagnostic info for GridDhtTxFinishFuture.

commit 0f9a895a04cd4a4f6be8e006fc2afd6f720b2215
Author: sboikov 
Date:   2017-07-05T11:25:16Z

Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2

commit 15da654a3e5c2bbf14947f0d3dd08270a9ba6766

[jira] [Created] (IGNITE-5704) Do not allow cluster to be deactivated if the joining node does not complete start all components

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-5704:
--

 Summary: Do not allow cluster to be deactivated if the joining 
node does not complete start all components
 Key: IGNITE-5704
 URL: https://issues.apache.org/jira/browse/IGNITE-5704
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.0, 2.1
Reporter: Dmitriy Govorukhin
Assignee: Dmitriy Govorukhin
Priority: Critical
 Fix For: 2.2






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5703) Add CREATE TABLE param for cache write sync mode

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-5703:
---

 Summary: Add CREATE TABLE param for cache write sync mode
 Key: IGNITE-5703
 URL: https://issues.apache.org/jira/browse/IGNITE-5703
 Project: Ignite
  Issue Type: Task
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
 Fix For: 2.1


Inspired by IGNITE-5702: instead of always enforcing {{FULL_SYNC}} mode, we 
better give the user an opportunity to set it explicitly like we do with other 
params (backups number, atomicity mode, etc.).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2246: IGNITE-5702

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

https://github.com/apache/ignite/pull/2246

IGNITE-5702



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5702

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2246.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2246






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Apache Ignite 2.1 scope

[Vyacheslav Daradur]

Hi Igniters!

When code freeze of v.2.1 is planned?

>> tickets which will not be ready by the end of the week to the next
release.
7 July?

2017-07-04 18:39 GMT+03:00 Vladimir Ozerov :

> Igniters,
>
> We have 536 tickets assinged to 2.1 release [1]. I propose to move all the
> tickets which will not be ready by the end of the week to the next release.
> You may use this report [2], which will show all the issues which are
> either reported by you or assigned to you (you must be logged in to JIRA to
> get correct results).
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20IGNITE%20AND%20status%20not%20in%20(Resolved%2C%
> 20Closed)%20AND%20fixVersion%20%3D%202.1
> [2]
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20IGNITE%20AND%20status%20not%20in%20(Resolved%2C%
> 20Closed)%20AND%20fixVersion%20%3D%202.1%20AND%20(assignee%
> 20%3D%20currentUser()%20or%20reporter%20%3D%20currentUser())
>
> On Tue, Jul 4, 2017 at 1:20 PM, Vladimir Ozerov 
> wrote:
>
> > Igniters,
> >
> > Persistent store has been merged to master branch! "master-bak" branch
> was
> > created to keep the state before merge for safety. As release date for
> 2.1
> > is mid July, I created "ignite-2.1" branch where we will stabilize the
> > release as usual. Please push features and fixes planned for 2.1 release
> to
> > this branch. The rest commits should go to master.
> >
> > Vladimir.
> >
> > On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov 
> > wrote:
> >
> >> Hi Denis,
> >>
> >> Awesome news! I'll take care of necessary release procedures if nobody
> >> minds.
> >>
> >> Vladimir.
> >>
> >> On Sat, Jul 1, 2017 at 12:25 AM, Denis Magda  wrote:
> >>
> >>> 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, it’s absolutely fine to make it
> >>> available in the nearest release.
> >>>
> >>> My proposal is to do the release by mid of July (closer to July 15th).
> >>> Is there anyone who is ready to take over as a release manager
> creating the
> >>> page like this [2] and handling all release related activities?
> >>>
> >>>
> >>> [1] http://apache-ignite-developers.2346864.n4.nabble.com/Ignite
> >>> -Persistent-Store-Ready-for-merge-td19160.html
> >>> [2] https://cwiki.apache.org/confluence/display/IGNITE/
> Apache+Ignite+2.0
> >>>
> >>> —
> >>> Denis
> >>>
> >>> > On Jun 1, 2017, at 9:24 AM, Alexander Paschenko <
> >>> alexander.a.pasche...@gmail.com> wrote:
> >>> >
> >>> > IGNITE-5327 Create predefined cache templates for CREATE TABLE
> command
> >>> > - minor comments left, ETA is Friday.
> >>> >
> >>> > IGNITE-5380 Validate cache QueryEntities in discovery thread - in
> >>> > progress, the meat of code is written, but need to add lots of tests.
> >>> > ETA is Friday.
> >>> >
> >>> > IGNITE-5188 Support AFFINITY KEY keyword for CREATE TABLE command -
> in
> >>> > progress, made few first small steps, ETA is Friday.
> >>> >
> >>> > Rest is closed/patch available, ignite-4994 has been moved to 2.2.
> >>> >
> >>> > - Alex
> >>> >
> >>> > 2017-06-01 19:03 GMT+03:00 Sergey Chugunov <
> sergey.chugu...@gmail.com
> >>> >:
> >>> >>   1. IGNITE-5386 Inactive mode must be forced on starting up grid
> with
> >>> >>   persistence is enabled
> >>> >>   It is important improvement to fix critical bug IGNITE-5363.
> >>> >>   Working on it, ETA - tomorrow.
> >>> >>   2. IGNITE-5375 New PersistentStoreMetrics, MemoryMetrics interface
> >>> >>   improvements
> >>> >>   A lot of discussions were on this topic, ticket created only today
> >>> and
> >>> >>   requires several days to implement.
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Thu, Jun 1, 2017 at 6:56 PM, Taras Ledkov 
> >>> wrote:
> >>> >>
> >>> >>> Folks,
> >>> >>>
> >>> >>> IGNITE-4922 JDBC Driver: renew thin client based solution:
> >>> >>>
> >>> >>> On 2.1 the functionality of the new thin client JDBC driver will be
> >>> >>> between deprecated Ignite thin JDBC and Ignite JDBCv2.
> >>> >>> 1. The most functions of SQL query (include DML) are implemented
> and
> >>> ready
> >>> >>> for review;
> >>> >>> 2. The most functions of JDBC metadata are implemented and ready
> for
> >>> >>> review;
> >>> >>> 3. Transactions, batching, streaming, blobs, scrollable / writable
> >>> cursors
> >>> >>> will not be supported in 2.1.
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>> On 01.06.2017 18:43, Vladimir Ozerov wrote:
> >>> >>>
> >>>  Folks,
> >>> 
> >>>  We are almost reached proposed feature-complete date (June 2),
> >>> Could you
> >>>  please share current status of your major features?
> >>> 
> >>>  On Tue, May 16, 2017 at 3:51 AM, Dmitriy Setrakyan <
> >>> 

[GitHub] ignite pull request #2245: ignite-gg-12450 Add onActivate/onDeactivate metho...

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

https://github.com/apache/ignite/pull/2245

ignite-gg-12450 Add onActivate/onDeactivate methods plugin providers



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12450

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2245.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2245


commit 6bffcb2af8deee2afdba7ed338a8949287a4a25d
Author: Dmitriy Govorukhin 
Date:   2017-07-05T14:23:49Z

ignite-gg-12450 Add onActivate/onDeactivate methods for GridPluginProcessor




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2237: IGNITE-5663: ODBC: Closing cursor do not reset pr...

[isapego]

Github user isapego closed the pull request at:

https://github.com/apache/ignite/pull/2237


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2161: IGNITE-5133: Examples return non-zero on error no...

[isapego]

Github user isapego closed the pull request at:

https://github.com/apache/ignite/pull/2161


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2148: IGNITE-5525: Fix for ODBC example

[isapego]

Github user isapego closed the pull request at:

https://github.com/apache/ignite/pull/2148


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2244: IGNITE-5604 expand byteBuffer for wal iterator if...

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

https://github.com/apache/ignite/pull/2244

IGNITE-5604 expand byteBuffer for wal iterator if record size more that 
current buffer size



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5604

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2244.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2244


commit acc49072e76588b5bc6c06e3fd329b82a86c87b0
Author: Dmitriy Govorukhin 
Date:   2017-07-05T12:19:10Z

ignite-5604 expand byteBuffer for wal iterator if record size more that 
current buffer size




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2212: IGNITE-5598: Fixed switch segment record, WAL rea...

[dspavlov]

Github user dspavlov closed the pull request at:

https://github.com/apache/ignite/pull/2212


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2198: Ignite 5591: WAL QueueFlusher replaced with sched...

[dspavlov]

Github user dspavlov closed the pull request at:

https://github.com/apache/ignite/pull/2198


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2207: Ignite 5589: Archive WAL segment after significan...

[dspavlov]

Github user dspavlov closed the pull request at:

https://github.com/apache/ignite/pull/2207


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2196: Ignite 5587: Generate File WAL Segment Archive Co...

[dspavlov]

Github user dspavlov closed the pull request at:

https://github.com/apache/ignite/pull/2196


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5700) Port range defines in addresses should override TcpDiscoverySpi.localPortRange

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-5700:
-

 Summary: Port range defines in addresses  should override 
TcpDiscoverySpi.localPortRange
 Key: IGNITE-5700
 URL: https://issues.apache.org/jira/browse/IGNITE-5700
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Evgenii Zhuravlev
Priority: Minor


If addresses were configured with
{code:java}



127.0.0.1:47500..47502


{code}

with default localPortRange(100) it's possible for node to bind on 47503 port.
If localPortRange was set to 0, node can't join to 47501 port.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: It seems WebSession's removeAttribute does not support HttpSessionBindingListener

[yucigou]

Ignite WebSessionV2 uses genuineSes as the original HttpSession.

Therefore, when setting an attribute or setting the maxInactiveInterval,
Ignite should tell the original HttpSession about it.

Otherwise, when the web container (such as Tomcat) thinks that a session
expires, or is invalidated, or a session attribute gets removed, etc.,
session attributes' HttpSessionBindingListener's valueUnbound callback
function will not get fired.

So once the original HttpSession gets updated with the session attributes
and the maxInactiveInterval, the web container will transitively trigger the
session attributes' HttpSessionBindingListener's valueUnbound callback
function when a session expires, etc.

(By the way, tested with our app, and our issue is fixed:
https://github.com/apache/ignite/pull/2243)





--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/It-seems-WebSession-s-removeAttribute-does-not-support-HttpSessionBindingListener-tp19184p19480.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request #2243: IGNITE-5607: HttpSessionBindingListener is not su...

[yucigou]

GitHub user yucigou opened a pull request:

https://github.com/apache/ignite/pull/2243

IGNITE-5607: HttpSessionBindingListener is not supported for clustere…

Ignite WebSessionV2 uses genuineSes as the original HttpSession.

Therefore, when setting an attribute or setting the maxInactiveInterval, 
Ignite should tell the original HttpSession about it.

Otherwise, when the web container (such as Tomcat) thinks that a session 
expires, or is invalidated, or a session attribute gets removed, etc., session 
attributes' HttpSessionBindingListener's valueUnbound callback function will 
not get fired.

So once the original HttpSession gets updated with the session attributes 
and the maxInactiveInterval, the web container will transitively trigger the 
session attributes' HttpSessionBindingListener's valueUnbound callback function 
when a session expires, etc.

(By the way, tested with our app, and our issue is fixed:

http://apache-ignite-developers.2346864.n4.nabble.com/It-seems-WebSession-s-removeAttribute-does-not-support-HttpSessionBindingListener-td19184.html)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/EuropePMC/ignite master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2243.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2243


commit eaaee978d37c5a66dff2d59515ddb70c40d5e31b
Author: Yuci Gou 
Date:   2017-07-05T10:26:57Z

IGNITE-5607: HttpSessionBindingListener is not supported for clustered web 
session




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: IGNITE-5468 ticket description looks confusing.

[Yakov Zhdanov]

Let me review when I am back next week.

--
Yakov Zhdanov

Re: abbrevation rules plugin

[Dmitry Pavlov]

Hi, I have created https://issues.apache.org/jira/browse/IGNITE-5698 for
this task.

It is not clear for me yet how to publish correctly - is it possible to
publish JAR.

ср, 5 июл. 2017 г. в 11:34, ALEKSEY KUZNETSOV :

> Yeah, it would be very helpful.
>
> вт, 4 июл. 2017 г. в 18:40, Dmitry Pavlov :
>
> > Hi, Val,
> >
> > No, this plugin is not available in apache-ignite code base.
> > May be we should remove reference from JIRA or add this plugin (and also
> > other code inspections) into AI code base.
> > Thoughts?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com>:
> >
> > > The plugin actually exists, not sure why it's not attached. Does anyone
> > has
> > > it?
> > >
> > > -Val
> > >
> > > On Mon, Jul 3, 2017 at 5:27 AM, ALEKSEY KUZNETSOV <
> > > alkuznetsov...@gmail.com>
> > > wrote:
> > >
> > > > Igntrs!
> > > > There is a plugin , mentioned  in Abbreviation Rules
> > > > <
> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules
> > >
> > > > page
> > > > that performs on-the-fly check.Is somebody going to add it some day?
> > > > --
> > > >
> > > > *Best Regards,*
> > > >
> > > > *Kuznetsov Aleksey*
> > > >
> > >
> >
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

[jira] [Created] (IGNITE-5699) Auto registration of keyFieldName and valueFieldName in queryFields

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-5699:
-

 Summary: Auto registration of keyFieldName and valueFieldName in 
queryFields
 Key: IGNITE-5699
 URL: https://issues.apache.org/jira/browse/IGNITE-5699
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Vasiliy Sisko


Now in QueryEntity when keyFieldName and valueFieldName fields are configured 
they should be described in fields map too. This action is misleading and badly 
described in documentation. 
We have all information to auto registration of that aliases in fields map. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5698) Publish Abbreviation Plugin in apache ignite

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5698:
--

 Summary: Publish Abbreviation Plugin in apache ignite
 Key: IGNITE-5698
 URL: https://issues.apache.org/jira/browse/IGNITE-5698
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov


Reported at dev list
http://apache-ignite-developers.2346864.n4.nabble.com/abbrevation-rules-plugin-td19356.html

There is a plugin , mentioned  in Abbreviation Rules 
 page 
that performs on-the-fly check.

https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules#AbbreviationRules-IntelliJIdeaPlugin



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: IGNITE-5468 ticket description looks confusing.

[Andrey Mashenkov]

Yes, Yakov. I mean query with join of 2 caches can be run on either of it.

Second parameter is merge prefetch size. You can see they going together in
PR.

5 июля 2017 г. 11:48 пользователь "Yakov Zhdanov" 
написал:

> Same query against different caches? This sounds like same query against
> different tables. :) Andrey can you please provide real-world example?
>
> What 2 params do you mean? Which one is the second?
>
> My points are:
> - provide ability to set limits without restarting the cluster.
> - provide ability to set limits per query as different queries may require
> different resources and having one hard limit for all the queries seems to
> be very inconvenient.
>
> Ideally, I would get rid of this IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
> and use just memory limits - if query runs out of memory then it is
> cancelled with proper error message, but I doubt if this can be done
> quickly.
>
> --
> Yakov Zhdanov
>

[GitHub] ignite pull request #2242: Ignite 1.8.8 p1

[ezhuravl]

GitHub user ezhuravl opened a pull request:

https://github.com/apache/ignite/pull/2242

Ignite 1.8.8 p1



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.8-p1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2242.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2242


commit f9aaf0353cea54afefea4caac74b1583eb17969b
Author: agura 
Date:   2017-01-18T15:04:45Z

ignite-4499 Drop node from topology in case when connection creation is 
impossible

commit d396398c1b4660b3bca24d2650a10f6c0677b4df
Author: sboikov 
Date:   2016-12-02T07:36:41Z

ignite-4314 cache.clear should not destroy offheap map

(cherry picked from commit 88c06ec)

commit 51e1f874624c428cc93e9c16407ec5a8b4cf8420
Author: sboikov 
Date:   2017-01-19T07:52:42Z

Throw CacheException from queries API.

commit 9c9175d4a84194a224a4020e6185d1e2aee0a5aa
Author: dkarachentsev 
Date:   2017-01-19T08:19:18Z

ignite-4147 - Rollback due to test failing on many restarts, should be 
improved to be more durable

commit f35057833900ba028b3a9a8bd547df61f42a45ed
Author: sboikov 
Date:   2017-01-19T09:44:57Z

CacheScanPartitionQueryFallbackSelfTest fixed to use default page size.

commit 71a76c81530d1aa38525fd78a90b065b6e19a6bb
Author: Andrey V. Mashenkov 
Date:   2017-01-19T10:29:55Z

IGNITE-4550: Move service deployment to certain test. This closes #1437.

commit 476b089b1dd4b4c5d3b6ae21e1b3b2c010c086ac
Author: tledkov-gridgain 
Date:   2017-01-20T14:33:34Z

IGNITE-4507: Hadoop: added direct output support for combiner. This closes 
#1434.

commit 065fe4525cc46a46f65dd40af6f4be9f034c0de2
Author: devozerov 
Date:   2017-01-20T14:36:02Z

Merge remote-tracking branch 'upstream/ignite-1.8.3' into ignite-1.8.3

commit 09ed12847422b265a60d7217530b98728363688b
Author: sboikov 
Date:   2017-01-23T08:20:57Z

Merge remote-tracking branch 'remotes/community/ignite-1.7.6' into 
ignite-1.8.3

commit db84b9b6e39ac37791b35479bccb8bbd75bb1676
Author: sboikov 
Date:   2017-01-23T08:26:18Z

Merge ignite-4499.

commit 7f0af43519f9e27f84ce8106d98b90aff00ee936
Author: sboikov 
Date:   2017-01-23T11:14:22Z

Added benchmark.

commit e832ef9ce363fad34097aa78293a57f4aefcbcc0
Author: Anton Vinogradov 
Date:   2017-01-24T11:44:33Z

IGNITE-3699 (Backported from master) CreatedExpiryPolicy doesn't work if 
entry is loaded from store

commit 3db0971d7d32798aeb3ce5dd8c0b3246a895fe91
Author: devozerov 
Date:   2017-01-24T13:45:59Z

IGNITE-4598: Hadoop: implemented raw comparator for BytesWritable key type. 
This closes #1457.

commit d3e2e0c5574f7677645e73e1fbafaee3563895f1
Author: Andrey Novikov 
Date:   2017-01-25T07:27:01Z

Merge branches 'ignite-1.7.6' and 'web-console-production' of 
https://github.com/gridgain/apache-ignite into web-console-production

commit 295f80d10da02692540435d46961a9c3cca99b3c
Author: Andrey Novikov 
Date:   2017-01-25T06:58:57Z

IGNITE-4520 Added credential request for authentication on proxy.

(cherry picked from commit ef04f35)

commit f25f85afb9d9d5e91116086a6b3998a5bbb082b9
Author: Andrey Novikov 
Date:   2017-01-25T06:58:57Z

IGNITE-4520 Added credential request for authentication on proxy.

(cherry picked from commit ef04f35)

commit ccc0f41794bfd2deecc3e0bd042f82d81c9809d0
Author: Vasiliy Sisko 
Date:   2017-01-20T09:22:24Z

IGNITE-4548 CacheJdbcStore: support mapping of enum types.

(cherry picked from commit f1fca3a)

commit 6f6ff397c8a2fb3f1041958a3338294cb44af998
Author: Andrey Novikov 
Date:   2017-01-25T09:48:05Z

IGNITE-1596 Fixed version sort.

(cherry picked from commit 128ba07)

commit faa20530a707014ac34477cba8adaaa4b67de1bb
Author: Andrey Novikov 
Date:   2017-01-25T09:48:05Z

IGNITE-1596 Fixed version sort.

(cherry picked from commit 128ba07)

commit 9d9e61fc9db0f79daaa87b7ec2c89c652bd3beaa
Author: sboikov 
Date:   2017-01-25T11:37:57Z

Added benchmark IgnitePutOffHeapIndexedValue8Benchmark.

commit f5e601e2973bfa81593241e55e4b6f97c0e55c3c
Author: dkarachentsev 
Date:   2017-01-26T07:18:34Z

IGNITE-4036 - Fix. Near cache is not expired together with corresponding 
server cache

commit 898fa150c7e2a663685abf37c6d1bcd547910f0e
Author: Andrey Novikov 
Date:   

Re: IGNITE-5468 ticket description looks confusing.

[Yakov Zhdanov]

Same query against different caches? This sounds like same query against
different tables. :) Andrey can you please provide real-world example?

What 2 params do you mean? Which one is the second?

My points are:
- provide ability to set limits without restarting the cluster.
- provide ability to set limits per query as different queries may require
different resources and having one hard limit for all the queries seems to
be very inconvenient.

Ideally, I would get rid of this IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
and use just memory limits - if query runs out of memory then it is
cancelled with proper error message, but I doubt if this can be done
quickly.

--
Yakov Zhdanov

Re: IGNITE-5123

[Evgeniy Ignatiev]

Would you mind if I pick the 
https://issues.apache.org/jira/browse/IGNITE-5123 and place 
PluginProvider#onIgniteStart after the component callbacks are called to 
comply with its Javadoc?



On 04.07.2017 18:06, Evgeniy Ignatiev wrote:
As it is explicitly stated in Javadoc of PluginProvider#onIgniteStart 
that all internal components should be started before this method is 
called, which is not true, as internal component callbacks are called 
right after the PluginProvider#onIgniteStart.


On 7/2/2017 12:58 PM, Evgeniy Ignatiev wrote:

Hello, Igniters.

Looking at the ticket 
https://issues.apache.org/jira/browse/IGNITE-5123, the 
IgniteKernal#start notifies plugin providers, calling 
PluginProvider#onIgniteStart, before components are notified, when 
caches are created in GridCacheProcessor#onIgniteStart. Does it make 
sense to move plugin providers notification after components are 
notified, probably right before lifecycle beans notification, so to 
ensure that caches are started before PluginProvider#onIgniteStart 
method is called?

Re: abbrevation rules plugin

[ALEKSEY KUZNETSOV]

Yeah, it would be very helpful.

вт, 4 июл. 2017 г. в 18:40, Dmitry Pavlov :

> Hi, Val,
>
> No, this plugin is not available in apache-ignite code base.
> May be we should remove reference from JIRA or add this plugin (and also
> other code inspections) into AI code base.
> Thoughts?
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
>
> > The plugin actually exists, not sure why it's not attached. Does anyone
> has
> > it?
> >
> > -Val
> >
> > On Mon, Jul 3, 2017 at 5:27 AM, ALEKSEY KUZNETSOV <
> > alkuznetsov...@gmail.com>
> > wrote:
> >
> > > Igntrs!
> > > There is a plugin , mentioned  in Abbreviation Rules
> > >  >
> > > page
> > > that performs on-the-fly check.Is somebody going to add it some day?
> > > --
> > >
> > > *Best Regards,*
> > >
> > > *Kuznetsov Aleksey*
> > >
> >
>
-- 

*Best Regards,*

*Kuznetsov Aleksey*

[jira] [Created] (IGNITE-5697) Web Console should be configurable for IPv4 connections

[Michael Griggs (JIRA)]

Michael Griggs created IGNITE-5697:
--

 Summary: Web Console should be configurable for IPv4 connections
 Key: IGNITE-5697
 URL: https://issues.apache.org/jira/browse/IGNITE-5697
 Project: Ignite
  Issue Type: Bug
  Components: UI
Affects Versions: 2.0
Reporter: Michael Griggs
 Fix For: 2.1


When an IPv6 network interface is available, NodeJS will always prefer that to 
an IPv4 interface.  This causes problems if IPv6 is not fully operational on 
the network.  

This fix will add the ability to specify that IPv4 should be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)