Re: Lucene text index persistent ?

[Ivan Pavlukhin]

Hi Manu,

As I understood you provide a link to samples showing how extensions
could be used. Do you know whether source code for extensions
(persistent text indices, etc.) is available?

Best regards,
Ivan Pavlukhin

пн, 17 февр. 2020 г. в 20:48, Ivan Pavlukhin :
>
> Hi Manu,
>
> As I understood you provide a link to samples showing how extensions
> could be used. Do you know whether source code for extensions
> (persistent text indices, etc.) is available?
>
> Best regards,
> Ivan Pavlukhin
>
> пн, 10 февр. 2020 г. в 14:03, Manu :
> >
> > Hi! take a look to
> > https://github.com/hawkore/examples-apache-ignite-extensions/ they are
> > implemented a solution for persisted lucene and spatial indexes
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Ignite 2.8 documentation

[Denis Magda]

Artem,

Thanks for stepping in and preparing the list of top priority documentation
tasks! How about labeling those tickets somehow and creating a filter
similar to this one [1] but for "Required & Unresolved Documentation
Tasks"? I would simply add this as a new section to the Ignite 2.8 release
wiki page for ease of tracking and start working with the guys contributed
improvements directly. Will see the names of the authors who need to be
involved ;)

*Alexey Zinoviev*, there are many ML related changes coming in the release.
Could you check existing ML docs and suggest any changes?

[1]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks

-
Denis


On Wed, Feb 19, 2020 at 11:14 AM Artem Budnikov 
wrote:

> Maxim,
>
> One note from my side, I think we can move disk page compression [1]
> > to the 2-nd priority, but definitely must document WAL page
> > compression first [2]
>
>
> OK, good to know.
>
> On Wed, Feb 19, 2020 at 6:48 PM Maxim Muzafarov  wrote:
>
> > Artem,
> >
> >
> > Thank you for starting this thread.
> > One note from my side, I think we can move disk page compression [1]
> > to the 2-nd priority, but definitely must document WAL page
> > compression first [2]
> >
> >
> > The list of important tasks [3].
> > The list of documentation tasks [4].
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-10330
> > [2] https://issues.apache.org/jira/browse/IGNITE-11336
> > [3]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Themostimportantreleasetasks
> > [4]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks
> >
> > On Wed, 19 Feb 2020 at 18:15, Artem Budnikov
> >  wrote:
> > >
> > > Hi everyone,
> > >
> > > As the release of Ignite 2.8 is getting closer, let's discuss which
> > features should be documented. I created a list of features based on the
> > release notes and the documentation tickets in jira (see below). Much
> more
> > has been added, but these seemed to have first priority. It's not to say
> > that other features are not important, but given the limited resources a
> > list of high-priority task would help to schedule the time of those who
> > will help with the docs.
> > >
> > > Here is the list of features:
> > >
> > > Disk page compression
> > > Metrics and System Views documentation
> > > Default Ignite work dir location
> > > Baseline auto-adjust feature
> > > Cluster (de)activation events documentation
> > > Remove SqlQuery documentation
> > > Partition awareness for thin clients
> > > Transactions support in thin clients
> > > KILL QUERY command
> > > Move rebalance configuration properties to the IgniteConfiguration
> level
> > > Renamed IGNITE schema to SYS
> > > JDBC: Support for query cancellation
> > > JDBC: Support for query timeout
> > > suspend/resume for pessimistic transactions
> > >
> > > Now, two really big questions here:
> > >
> > > If you want to add anything else to the documentation, please let us
> > know in this thread.
> > > If you are the author of any of the features listed above, please share
> > the details on the feature. You can do it by creating a documentation
> > ticket. If you want to contribute a page or section to the existing docs,
> > you can write directly on apacheignite.readme.io (send me a note if you
> > don't have an account there). Any help is greatly appreciated.
> > >
> > > -Artem
> > >
> > >
> >
>

[jira] [Created] (IGNITE-12706) Bundle logback as optional lib

[Koala Lam (Jira)]

Koala Lam created IGNITE-12706:
--

 Summary: Bundle logback as optional lib
 Key: IGNITE-12706
 URL: https://issues.apache.org/jira/browse/IGNITE-12706
 Project: Ignite
  Issue Type: Improvement
Reporter: Koala Lam


Need logback-core and logback-classic



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

[Saikat Maitra]

Congratulations!!!

Regards
Saikat

On Wed, 19 Feb 2020 at 6:28 AM, Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:

> Congrats, keep up a good work!
>
> ср, 19 февр. 2020 г. в 13:20, Pavel Kovalenko :
>
> > Congratulations Slava!
> >
> > On Tue 18. Feb 2020 at 22.20, Dmitriy Pavlov  wrote:
> >
> > > Hello Ignite Community,
> > >
> > > The Project Management Committee (PMC) for Apache Ignite has invited
> > > Vyacheslav Koptilin to become a committer and we are pleased to
> announce
> > > that he has accepted.
> > >
> > > Vyacheslav investigated and fixed a number of non-trivial issues in the
> > > Ignite Native persistent store, was a reviewer of Read Repair (ex.
> > > Consistency Check).
> > >
> > > Being a committer enables easier contribution to the project since
> there
> > is
> > > no need to go via the patch submission process. This should enable
> better
> > > productivity.
> > >
> > > Vyacheslav, thanks for supporting the community and keep the pace!
> > >
> > > Best Regards,
> > > Dmitriy Pavlov
> > > on behalf of Apache Ignite PMC
> > >
> >
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>

[jira] [Created] (IGNITE-12705) Schedule rebalancing of SYNC caches with high priority

[Vyacheslav Koptilin (Jira)]

Vyacheslav Koptilin created IGNITE-12705:


 Summary: Schedule rebalancing of SYNC caches with high priority
 Key: IGNITE-12705
 URL: https://issues.apache.org/jira/browse/IGNITE-12705
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.8
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin
 Fix For: 2.9


In current implementation order in which rebalancing is triggered seems to be 
arbitrary, regardless of the configured rebalanceMode. In this case 
Ignition.start() method is forced to wait not only for rebalancing of SYNC 
caches, but also the ones that are scheduled for rebalancing before it.
This behavior should be fixed by making SYNC caches rebalance first, before 
going to any other caches.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Ignite 2.8 documentation

[Artem Budnikov]

Maxim,

One note from my side, I think we can move disk page compression [1]
> to the 2-nd priority, but definitely must document WAL page
> compression first [2]


OK, good to know.

On Wed, Feb 19, 2020 at 6:48 PM Maxim Muzafarov  wrote:

> Artem,
>
>
> Thank you for starting this thread.
> One note from my side, I think we can move disk page compression [1]
> to the 2-nd priority, but definitely must document WAL page
> compression first [2]
>
>
> The list of important tasks [3].
> The list of documentation tasks [4].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-10330
> [2] https://issues.apache.org/jira/browse/IGNITE-11336
> [3]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Themostimportantreleasetasks
> [4]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks
>
> On Wed, 19 Feb 2020 at 18:15, Artem Budnikov
>  wrote:
> >
> > Hi everyone,
> >
> > As the release of Ignite 2.8 is getting closer, let's discuss which
> features should be documented. I created a list of features based on the
> release notes and the documentation tickets in jira (see below). Much more
> has been added, but these seemed to have first priority. It's not to say
> that other features are not important, but given the limited resources a
> list of high-priority task would help to schedule the time of those who
> will help with the docs.
> >
> > Here is the list of features:
> >
> > Disk page compression
> > Metrics and System Views documentation
> > Default Ignite work dir location
> > Baseline auto-adjust feature
> > Cluster (de)activation events documentation
> > Remove SqlQuery documentation
> > Partition awareness for thin clients
> > Transactions support in thin clients
> > KILL QUERY command
> > Move rebalance configuration properties to the IgniteConfiguration level
> > Renamed IGNITE schema to SYS
> > JDBC: Support for query cancellation
> > JDBC: Support for query timeout
> > suspend/resume for pessimistic transactions
> >
> > Now, two really big questions here:
> >
> > If you want to add anything else to the documentation, please let us
> know in this thread.
> > If you are the author of any of the features listed above, please share
> the details on the feature. You can do it by creating a documentation
> ticket. If you want to contribute a page or section to the existing docs,
> you can write directly on apacheignite.readme.io (send me a note if you
> don't have an account there). Any help is greatly appreciated.
> >
> > -Artem
> >
> >
>

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

[Maxim Muzafarov]

Ilya,


I think we must accept only blocker issues to the release branch.

My previous experience tells me that even a small change which seems
absolutely easy and clear can break everything. So, let's move this
issue [1] to the next release. Currently, it doesn't look like a
blocker.

[1] https://issues.apache.org/jira/browse/IGNITE-12672

On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov  wrote:
>
> Igniters,
>
>
> I've prepared the issue [1] and PR [2] with removing @deprecate
> annotation on DataRegionMetrics and adding @IgniteExperimental to the
> new metrics API.
> Can anyone review my changes?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12690
> [2] https://github.com/apache/ignite/pull/7440
>
> On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev  
> wrote:
> >
> > Hello!
> >
> > I have just merged a fix for embarrassing issue where you could UPDATE
> > entries with Spring Data, but not "Update" or "update" them.
> >
> > I suggest adding this fix to the scope of 2.8, since Spring Data is popular
> > and it does not in any way affect code outside of its modules.
> >
> > https://issues.apache.org/jira/browse/IGNITE-12672
> >
> > WDYT?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov :
> >
> > > Alexey,
> > >
> > >
> > > Yes. I will remove @deprecation according to the vote results and will
> > > go further with the release steps [1] since there no blockers left.
> > >
> > >
> > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >
> > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > >  wrote:
> > > >
> > > > Folks,
> > > >
> > > > I have merged IGNITE-12650 (mark MVCC as experimental) to master and
> > > > ignite-2.8. What's left? Should we remove deprecation from the old
> > > metrics
> > > > and start the vote?
> > >

Re: Ignite 2.8 documentation

[Maxim Muzafarov]

Artem,


Thank you for starting this thread.
One note from my side, I think we can move disk page compression [1]
to the 2-nd priority, but definitely must document WAL page
compression first [2]


The list of important tasks [3].
The list of documentation tasks [4].

[1] https://issues.apache.org/jira/browse/IGNITE-10330
[2] https://issues.apache.org/jira/browse/IGNITE-11336
[3] 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Themostimportantreleasetasks
[4] 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks

On Wed, 19 Feb 2020 at 18:15, Artem Budnikov
 wrote:
>
> Hi everyone,
>
> As the release of Ignite 2.8 is getting closer, let's discuss which features 
> should be documented. I created a list of features based on the release notes 
> and the documentation tickets in jira (see below). Much more has been added, 
> but these seemed to have first priority. It's not to say that other features 
> are not important, but given the limited resources a list of high-priority 
> task would help to schedule the time of those who will help with the docs.
>
> Here is the list of features:
>
> Disk page compression
> Metrics and System Views documentation
> Default Ignite work dir location
> Baseline auto-adjust feature
> Cluster (de)activation events documentation
> Remove SqlQuery documentation
> Partition awareness for thin clients
> Transactions support in thin clients
> KILL QUERY command
> Move rebalance configuration properties to the IgniteConfiguration level
> Renamed IGNITE schema to SYS
> JDBC: Support for query cancellation
> JDBC: Support for query timeout
> suspend/resume for pessimistic transactions
>
> Now, two really big questions here:
>
> If you want to add anything else to the documentation, please let us know in 
> this thread.
> If you are the author of any of the features listed above, please share the 
> details on the feature. You can do it by creating a documentation ticket. If 
> you want to contribute a page or section to the existing docs, you can write 
> directly on apacheignite.readme.io (send me a note if you don't have an 
> account there). Any help is greatly appreciated.
>
> -Artem
>
>

Re: Apache Ignite downloads are redirecting from https to http

[Ilya Kasnacheev]

Hello!

I have fixed these links, now they point to HTTPS. Please check that it
would work now.

Regards,
-- 
Ilya Kasnacheev


ср, 19 февр. 2020 г. в 16:49, Denis Magda :

> Peter,
>
> Would you mind checking this issue and suggest a proper solution?
>
> Dmitry,
>
> Might this be somehow related to the RPM changes ASF INFRA suggested to
> make?
>
> -
> Denis
>
>
> On Wed, Feb 19, 2020 at 4:33 AM Stephen Darlington <
> stephen.darling...@gridgain.com> wrote:
>
> > As seen in the user mailing list. Looks like there’s a redirect from a
> > https on apache.org to a non-https link. Is there anyone who can fi
> this?
> >
> > Regards,
> > Stephen
> >
> > > Begin forwarded message:
> > >
> > > From: Devin Anderson 
> > > Subject: Apache Ignite downloads are redirecting from https to http
> > > Date: 18 February 2020 at 01:42:14 GMT
> > > To: 
> > > Reply-To: u...@ignite.apache.org
> > >
> > > Hi all,
> > >
> > > I'm not sure if this is the correct mailing list to bring up this
> > issue.  If I'm writing the wrong mailing list, please let me know and
> I'll
> > gladly send my message to a more appropriate list/person.
> > >
> > > When I attempt to run `apt-get update` on Ubuntu 18.04 with the Apache
> > Ignite repository in /etc/apt/sources.list, the update fails due to an
> > https to http redirect.  Here's the output from stdout:
> > >
> > > --
> > >
> > > Hit:1 http://us.archive.ubuntu.com/ubuntu <
> > http://us.archive.ubuntu.com/ubuntu> bionic InRelease
> > > Hit:2 http://security.ubuntu.com/ubuntu <
> > http://security.ubuntu.com/ubuntu> bionic-security InRelease
> > > Hit:3 http://us.archive.ubuntu.com/ubuntu <
> > http://us.archive.ubuntu.com/ubuntu> bionic-updates InRelease
> > > Ign:4 https://downloads.apache.org/ignite/deb <
> > https://downloads.apache.org/ignite/deb> apache-ignite InRelease
> > > Err:5 https://downloads.apache.org/ignite/deb <
> > https://downloads.apache.org/ignite/deb> apache-ignite Release
> > >   Redirection from https to '
> > http://dl.bintray.com/apache/ignite-deb/dists/apache-ignite/Release <
> > http://dl.bintray.com/apache/ignite-deb/dists/apache-ignite/Release>' is
> > forbidden [IP: 88.99.95.219 443]
> > > Reading package lists...
> > >
> > > --
> > >
> > > ... and stderr:
> > >
> > > --
> > >
> > > E: The repository 'http://apache.org/dist/ignite/deb <
> > http://apache.org/dist/ignite/deb> apache-ignite Release' does not have
> a
> > Release file.
> > >
> > > --
> > >
> > > You can see the redirect for yourself by visiting:
> > >
> > > https://downloads.apache.org/ignite/deb <
> > https://downloads.apache.org/ignite/deb>
> > >
> > > ... and noting that your browser is redirected to:
> > >
> > > http://dl.bintray.com/apache/ignite-deb/ <
> > http://dl.bintray.com/apache/ignite-deb/>
> > >
> > > I found one or two other places on downloads.apache.org that
> redirected
> > to dl.bintray.com, and those instances appear to redirect to an https
> > URI, so this looks like a problem specific to the way redirects are
> > configured for Apache Ignite assets.
> > >
> > > Any ideas?
> > >
> > > Thanks,
> > > --
> > > Devin
> > >
> >
> >
> >
>

Ignite 2.8 documentation

[Artem Budnikov]

Hi everyone,

As the release of Ignite 2.8 is getting closer, let's discuss which 
features should be documented. I created a list of features based on the 
release notes and the documentation tickets in jira (see below). Much 
more has been added, but these seemed to have first priority. It's not 
to say that other features are not important, but given the limited 
resources a list of high-priority task would help to schedule the time 
of those who will help with the docs.


Here is the list of features:

 * Disk page compression
 * Metrics and System Views documentation
 * Default Ignite work dir location
 * Baseline auto-adjust feature
 * Cluster (de)activation events documentation
 * Remove SqlQuery documentation
 * Partition awareness for thin clients
 * Transactions support in thin clients
 * KILL QUERY command
 * Move rebalance configuration properties to the IgniteConfiguration level
 * Renamed IGNITE schema to SYS
 * JDBC: Support for query cancellation
 * JDBC: Support for query timeout
 * suspend/resume for pessimistic transactions

Now, two really big questions here:

1. If you want to add anything else to the documentation, please let us
   know in this thread.
2. If you are the author of any of the features listed above, please
   share the details on the feature. You can do it by creating a
   documentation ticket. If you want to contribute a page or section to
   the existing docs, you can write directly on apacheignite.readme.io
   (send me a note if you don't have an account there). Any help is
   greatly appreciated.

-Artem

[jira] [Created] (IGNITE-12704) Fail of recognition of default scheme in SQL queries.

[Vladimir Steshin (Jira)]

Vladimir Steshin created IGNITE-12704:
-

 Summary: Fail of recognition of default scheme in SQL queries.
 Key: IGNITE-12704
 URL: https://issues.apache.org/jira/browse/IGNITE-12704
 Project: Ignite
  Issue Type: Bug
Reporter: Vladimir Steshin


Got a connectionConnection conn = ...;

// execute() - is just a helper function. Creates prepared statement, pass 
params...

// Get all the tables.
List> lst = execute(conn, "select SCHEMA_NAME, TABLE_NAME from
SYS.TABLES");

for( List row : lst ){
String schemaName = (String)row.get(0);
String tableName = (String)row.get(1);

// Shows: "schema: default, table: PERSON"
System.out.println("schema: " +  schemName + ", table: " +
tableName));

// Fails with with: java.sql.SQLException: Failed to parse query.
Схема "DEFAULT" не найдена
execute( conn, "drop table "+schemaName + "."+tableName+"'" );
}

I think this case should fail with error like "only cache created tables
can be removed with drop table. ", not with "scheme not found."
SQL-engine is supposed to accept and understand values it returns itself.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-12703) Remove misleading references to the currently missing G.grid(null) method from public and internal javadocs.

[Pavel Pereslegin (Jira)]

Pavel Pereslegin created IGNITE-12703:
-

 Summary: Remove misleading references to the currently missing 
G.grid(null) method from public and internal javadocs.
 Key: IGNITE-12703
 URL: https://issues.apache.org/jira/browse/IGNITE-12703
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.9
Reporter: Pavel Pereslegin


We have some incorrect references to the missing G.grid() method in *public* 
(\{{Ignition#ignite()}}) and internal (\{{CacheQuery}}, \{{IgnitionEx#grid()}}) 
javadocs, which should be fixed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Ignite downloads are redirecting from https to http

[Denis Magda]

Peter,

Would you mind checking this issue and suggest a proper solution?

Dmitry,

Might this be somehow related to the RPM changes ASF INFRA suggested to
make?

-
Denis


On Wed, Feb 19, 2020 at 4:33 AM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:

> As seen in the user mailing list. Looks like there’s a redirect from a
> https on apache.org to a non-https link. Is there anyone who can fi this?
>
> Regards,
> Stephen
>
> > Begin forwarded message:
> >
> > From: Devin Anderson 
> > Subject: Apache Ignite downloads are redirecting from https to http
> > Date: 18 February 2020 at 01:42:14 GMT
> > To: 
> > Reply-To: u...@ignite.apache.org
> >
> > Hi all,
> >
> > I'm not sure if this is the correct mailing list to bring up this
> issue.  If I'm writing the wrong mailing list, please let me know and I'll
> gladly send my message to a more appropriate list/person.
> >
> > When I attempt to run `apt-get update` on Ubuntu 18.04 with the Apache
> Ignite repository in /etc/apt/sources.list, the update fails due to an
> https to http redirect.  Here's the output from stdout:
> >
> > --
> >
> > Hit:1 http://us.archive.ubuntu.com/ubuntu <
> http://us.archive.ubuntu.com/ubuntu> bionic InRelease
> > Hit:2 http://security.ubuntu.com/ubuntu <
> http://security.ubuntu.com/ubuntu> bionic-security InRelease
> > Hit:3 http://us.archive.ubuntu.com/ubuntu <
> http://us.archive.ubuntu.com/ubuntu> bionic-updates InRelease
> > Ign:4 https://downloads.apache.org/ignite/deb <
> https://downloads.apache.org/ignite/deb> apache-ignite InRelease
> > Err:5 https://downloads.apache.org/ignite/deb <
> https://downloads.apache.org/ignite/deb> apache-ignite Release
> >   Redirection from https to '
> http://dl.bintray.com/apache/ignite-deb/dists/apache-ignite/Release <
> http://dl.bintray.com/apache/ignite-deb/dists/apache-ignite/Release>' is
> forbidden [IP: 88.99.95.219 443]
> > Reading package lists...
> >
> > --
> >
> > ... and stderr:
> >
> > --
> >
> > E: The repository 'http://apache.org/dist/ignite/deb <
> http://apache.org/dist/ignite/deb> apache-ignite Release' does not have a
> Release file.
> >
> > --
> >
> > You can see the redirect for yourself by visiting:
> >
> > https://downloads.apache.org/ignite/deb <
> https://downloads.apache.org/ignite/deb>
> >
> > ... and noting that your browser is redirected to:
> >
> > http://dl.bintray.com/apache/ignite-deb/ <
> http://dl.bintray.com/apache/ignite-deb/>
> >
> > I found one or two other places on downloads.apache.org that redirected
> to dl.bintray.com, and those instances appear to redirect to an https
> URI, so this looks like a problem specific to the way redirects are
> configured for Apache Ignite assets.
> >
> > Any ideas?
> >
> > Thanks,
> > --
> > Devin
> >
>
>
>

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

[Alexei Scherbakov]

Congrats, keep up a good work!

ср, 19 февр. 2020 г. в 13:20, Pavel Kovalenko :

> Congratulations Slava!
>
> On Tue 18. Feb 2020 at 22.20, Dmitriy Pavlov  wrote:
>
> > Hello Ignite Community,
> >
> > The Project Management Committee (PMC) for Apache Ignite has invited
> > Vyacheslav Koptilin to become a committer and we are pleased to announce
> > that he has accepted.
> >
> > Vyacheslav investigated and fixed a number of non-trivial issues in the
> > Ignite Native persistent store, was a reviewer of Read Repair (ex.
> > Consistency Check).
> >
> > Being a committer enables easier contribution to the project since there
> is
> > no need to go via the patch submission process. This should enable better
> > productivity.
> >
> > Vyacheslav, thanks for supporting the community and keep the pace!
> >
> > Best Regards,
> > Dmitriy Pavlov
> > on behalf of Apache Ignite PMC
> >
>


-- 

Best regards,
Alexei Scherbakov

[jira] [Created] (IGNITE-12702) Print warning when a cache value contains @AffinityKeyMapped annotation

[Denis Mekhanikov (Jira)]

Denis Mekhanikov created IGNITE-12702:
-

 Summary: Print warning when a cache value contains 
@AffinityKeyMapped annotation
 Key: IGNITE-12702
 URL: https://issues.apache.org/jira/browse/IGNITE-12702
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Denis Mekhanikov


Consider the following code snippet:
{code:java}
public class WrongAffinityExample {
public static void main(String[] args) {
Ignite ignite = Ignition.start("config/ignite.xml");

IgniteCache cache = 
ignite.getOrCreateCache("employees");

EmployeeKey key = new EmployeeKey(1);
EmployeeValue value = new EmployeeValue(1, "Denis");
cache.put(key, value);
}

public static class EmployeeKey {
private int id;

public EmployeeKey(int id) {
this.id = id;
}
}

public static class EmployeeValue {
@AffinityKeyMapped
int departmentId;
String name;

public EmployeeValue(int departmentId, String name) {
this.departmentId = departmentId;
this.name = name;
}
}
}
{code}
Note, that {{EmployeeValue}} contains an {{@AffinityKeyMapped}} annotation, 
which doesn't have any effect, since it's specified in a value, and not in a 
key.

Such mistake is simple to make and pretty hard to track down.
 This configuration should trigger a warning message printed in log to let the 
user know that this affinity key configuration is not applied.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

[Pavel Kovalenko]

Congratulations Slava!

On Tue 18. Feb 2020 at 22.20, Dmitriy Pavlov  wrote:

> Hello Ignite Community,
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Vyacheslav Koptilin to become a committer and we are pleased to announce
> that he has accepted.
>
> Vyacheslav investigated and fixed a number of non-trivial issues in the
> Ignite Native persistent store, was a reviewer of Read Repair (ex.
> Consistency Check).
>
> Being a committer enables easier contribution to the project since there is
> no need to go via the patch submission process. This should enable better
> productivity.
>
> Vyacheslav, thanks for supporting the community and keep the pace!
>
> Best Regards,
> Dmitriy Pavlov
> on behalf of Apache Ignite PMC
>

[jira] [Created] (IGNITE-12701) Disallow silent deactivation in CLI and REST.

[Vladimir Steshin (Jira)]

Vladimir Steshin created IGNITE-12701:
-

 Summary: Disallow silent deactivation in CLI and REST.
 Key: IGNITE-12701
 URL: https://issues.apache.org/jira/browse/IGNITE-12701
 Project: Ignite
  Issue Type: Sub-task
Reporter: Vladimir Steshin
Assignee: Vladimir Steshin


Disallow silent deactivation through the CLI and REST. 

Skip JMX call 
{code:java}
void IgniteMXBean#active(boolean active)
{code}




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-12700) Calcite integration. Aggregates support.

[Igor Seliverstov (Jira)]

Igor Seliverstov created IGNITE-12700:
-

 Summary: Calcite integration. Aggregates support.
 Key: IGNITE-12700
 URL: https://issues.apache.org/jira/browse/IGNITE-12700
 Project: Ignite
  Issue Type: New Feature
  Components: sql
Reporter: Igor Seliverstov
Assignee: Igor Seliverstov






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

[Pavel Kovalenko]

Congratulations, Slava!
Don't let the bad code occupy master :)

вт, 18 февр. 2020 г. в 22:20, Dmitriy Pavlov :

> Hello Ignite Community,
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Vyacheslav Koptilin to become a committer and we are pleased to announce
> that he has accepted.
>
> Vyacheslav investigated and fixed a number of non-trivial issues in the
> Ignite Native persistent store, was a reviewer of Read Repair (ex.
> Consistency Check).
>
> Being a committer enables easier contribution to the project since there is
> no need to go via the patch submission process. This should enable better
> productivity.
>
> Vyacheslav, thanks for supporting the community and keep the pace!
>
> Best Regards,
> Dmitriy Pavlov
> on behalf of Apache Ignite PMC
>

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

[Alexey Zinoviev]

Slava, cool, good luck with merging to MASTER!!!

ср, 19 февр. 2020 г. в 11:45, Petr Ivanov :

> Congratulations!
>
>
> > On 18 Feb 2020, at 22:20, Dmitriy Pavlov  wrote:
> >
> > Hello Ignite Community,
> >
> > The Project Management Committee (PMC) for Apache Ignite has invited
> > Vyacheslav Koptilin to become a committer and we are pleased to announce
> > that he has accepted.
> >
> > Vyacheslav investigated and fixed a number of non-trivial issues in the
> > Ignite Native persistent store, was a reviewer of Read Repair (ex.
> > Consistency Check).
> >
> > Being a committer enables easier contribution to the project since there
> is
> > no need to go via the patch submission process. This should enable better
> > productivity.
> >
> > Vyacheslav, thanks for supporting the community and keep the pace!
> >
> > Best Regards,
> > Dmitriy Pavlov
> > on behalf of Apache Ignite PMC
>
>

Fwd: Apache Ignite downloads are redirecting from https to http

[Stephen Darlington]

As seen in the user mailing list. Looks like there’s a redirect from a https on 
apache.org to a non-https link. Is there anyone who can fi this?

Regards,
Stephen

> Begin forwarded message:
> 
> From: Devin Anderson 
> Subject: Apache Ignite downloads are redirecting from https to http
> Date: 18 February 2020 at 01:42:14 GMT
> To: 
> Reply-To: u...@ignite.apache.org
> 
> Hi all,
> 
> I'm not sure if this is the correct mailing list to bring up this issue.  If 
> I'm writing the wrong mailing list, please let me know and I'll gladly send 
> my message to a more appropriate list/person.
> 
> When I attempt to run `apt-get update` on Ubuntu 18.04 with the Apache Ignite 
> repository in /etc/apt/sources.list, the update fails due to an https to http 
> redirect.  Here's the output from stdout:
> 
> --
> 
> Hit:1 http://us.archive.ubuntu.com/ubuntu 
>  bionic InRelease
> Hit:2 http://security.ubuntu.com/ubuntu  
> bionic-security InRelease
> Hit:3 http://us.archive.ubuntu.com/ubuntu 
>  bionic-updates InRelease
> Ign:4 https://downloads.apache.org/ignite/deb 
>  apache-ignite InRelease
> Err:5 https://downloads.apache.org/ignite/deb 
>  apache-ignite Release
>   Redirection from https to 
> 'http://dl.bintray.com/apache/ignite-deb/dists/apache-ignite/Release 
> ' is 
> forbidden [IP: 88.99.95.219 443]
> Reading package lists...
> 
> --
> 
> ... and stderr:
> 
> --
> 
> E: The repository 'http://apache.org/dist/ignite/deb 
>  apache-ignite Release' does not have a 
> Release file.
> 
> --
> 
> You can see the redirect for yourself by visiting:
> 
> https://downloads.apache.org/ignite/deb 
> 
> 
> ... and noting that your browser is redirected to:
> 
> http://dl.bintray.com/apache/ignite-deb/ 
> 
> 
> I found one or two other places on downloads.apache.org that redirected to 
> dl.bintray.com, and those instances appear to redirect to an https URI, so 
> this looks like a problem specific to the way redirects are configured for 
> Apache Ignite assets.
> 
> Any ideas?
> 
> Thanks,
> -- 
> Devin
> 

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

[Petr Ivanov]

Congratulations!


> On 18 Feb 2020, at 22:20, Dmitriy Pavlov  wrote:
> 
> Hello Ignite Community,
> 
> The Project Management Committee (PMC) for Apache Ignite has invited
> Vyacheslav Koptilin to become a committer and we are pleased to announce
> that he has accepted.
> 
> Vyacheslav investigated and fixed a number of non-trivial issues in the
> Ignite Native persistent store, was a reviewer of Read Repair (ex.
> Consistency Check).
> 
> Being a committer enables easier contribution to the project since there is
> no need to go via the patch submission process. This should enable better
> productivity.
> 
> Vyacheslav, thanks for supporting the community and keep the pace!
> 
> Best Regards,
> Dmitriy Pavlov
> on behalf of Apache Ignite PMC

[jira] [Created] (IGNITE-12699) .NET: Remove TypeCaster

[Pavel Tupitsyn (Jira)]

Pavel Tupitsyn created IGNITE-12699:
---

 Summary: .NET: Remove TypeCaster
 Key: IGNITE-12699
 URL: https://issues.apache.org/jira/browse/IGNITE-12699
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.9


TypeCaster class is used in Ignite.NET for non-boxing, faster casts.
Benchmarks on .NET 4.0 displayed clear advantage of this solution.

However, this is no longer true on .NET Core due to improvements in the 
framework:

{code}
| Method |   Runtime |  Mean | Error |StdDev |
|--- |-- |--:|--:|--:|
| TypeCaster | .NET Core 2.2 | 3.4615 ns | 0.0325 ns | 0.0304 ns |
| ObjectCast | .NET Core 2.2 | 1.0936 ns | 0.0040 ns | 0.0036 ns |
| UnsafeCast | .NET Core 2.2 | 4.1921 ns | 0.0125 ns | 0.0111 ns |
| TypeCaster | .NET Core 3.1 | 1.5306 ns | 0.0042 ns | 0.0037 ns |
| ObjectCast | .NET Core 3.1 | 0.0229 ns | 0.0029 ns | 0.0024 ns |
| UnsafeCast | .NET Core 3.1 | 2.1868 ns | 0.0052 ns | 0.0043 ns |
{code}

(See benchmark code in https://github.com/ptupitsyn/IgniteNetBenchmarks)

Remove TypeCaster class and use regular cast instead.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

[Ilya Suntsov]

Congrats, Slava!

ср, 19 февр. 2020 г. в 10:59, Andrey Mashenkov :

> Congratulations, Slava!
>
> вт, 18 февр. 2020 г., 22:20 Dmitriy Pavlov :
>
> > Hello Ignite Community,
> >
> > The Project Management Committee (PMC) for Apache Ignite has invited
> > Vyacheslav Koptilin to become a committer and we are pleased to announce
> > that he has accepted.
> >
> > Vyacheslav investigated and fixed a number of non-trivial issues in the
> > Ignite Native persistent store, was a reviewer of Read Repair (ex.
> > Consistency Check).
> >
> > Being a committer enables easier contribution to the project since there
> is
> > no need to go via the patch submission process. This should enable better
> > productivity.
> >
> > Vyacheslav, thanks for supporting the community and keep the pace!
> >
> > Best Regards,
> > Dmitriy Pavlov
> > on behalf of Apache Ignite PMC
> >
>


-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com