MAC addresses emulation in Testing Framework

Hi, Igniters! I need your help about the following question: How to set-up (emulate) custom MAC address at node startup in Testing Framework? I need to write unit-test that checks requests distribution which depends on ClusterNodes MAC addresses. I tried to change it after instance startup via

[GitHub] ignite pull request #3609: IGNITE-6113 Return back old implementation instea...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3609 ---

Re: [VOTE] Apache Ignite 2.4.0 RC1

+1 (binding), downloaded Ignite from binaries and worked with it -- Denis On Mon, Mar 5, 2018 at 11:42 AM, Vladimir Ozerov wrote: > Igniters, > > We have uploaded a 2.4.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/2.4.0-rc1/ > > Git tag name is

Re: Thin client: transactions support

Here is an original discussion with a reference to the JIRA ticket: http://apache-ignite-developers.2346864.n4.nabble.com/Re-Transaction-operations-using-the-Ignite-Thin-Client-Protocol-td25914.html -- Denis On Tue, Mar 6, 2018 at 9:18 AM, Dmitriy Setrakyan wrote: > Hi

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hi Nikolay, Please note there is cluster-auto activation when it reaches baseline topology. As far as I remember to be PCI-DSS compliant it is sufficient to use encryption at file system level. But it needs to be double-checked. It requires encrypt transmission of cardholder data across open,

[GitHub] ignite pull request #3608: IGNITE-7889: .NET: linq GroupBy and Where does no...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3608 ---

Re: checksum file Release Distribution Policy

I don't see MD5 files anywhere on the website: https://ignite.apache.org/download.cgi Where do we have them? D. On Tue, Mar 6, 2018 at 4:50 AM, Vladimir Ozerov wrote: > I am not sure. We do have SHA512 files, which is ok. But we also have MD5 > files, which are now

[jira] [Created] (IGNITE-7893) Release Java Thin client documentation

Denis Magda created IGNITE-7893: --- Summary: Release Java Thin client documentation Key: IGNITE-7893 URL: https://issues.apache.org/jira/browse/IGNITE-7893 Project: Ignite Issue Type: New

Re: MAC addresses emulation in Testing Framework

Hi Vyacheslav, Why do you think reflection is bad in that case? Tests often use reflection, moreover U.field() to access some private stuff and test it. Sincerely, Dmitriy Pavlov вт, 6 мар. 2018 г. в 21:11, Vyacheslav Daradur : > Hi, Igniters! > > I need your help about

Re: [VOTE] Apache Ignite 2.4.0 RC1

Igniters, I appologize for querying probably well-known information: Is there any nexus repository, probably staging, which can be set up in gradle/maven in addition to https://mvnrepository.com/artifact/org.apache.ignite/ignite-core where this RC-1 is located? Could it be tested using simple

Re: Ignite nightly build job on Apache Jenkins server

I've started to accumulate information about our tests eco-system here https://cwiki.apache.org/confluence/display/IGNITE/Continuous+Integration (It draft now, I'll also send an announcing mail when it will be ready). I will add this link to the page also. ср, 7 мар. 2018 г. в 0:03, Dmitriy

Re: Ignite nightly build job on Apache Jenkins server

OK, fine, in that case please send out a link to the TC nightly builds whenever it is ready, so the community would know where to get it. On Tue, Mar 6, 2018 at 12:16 AM, Petr Ivanov wrote: > Amount of effort will exceed creating new build on TeamCity. > Currently on

Re: Let's keep Apache Ignite docs up-to-date

Guys, The migration process is in the progress. Here is a discussion where we exchanged alternate doc engines (let's keep talking there): http://apache-ignite-developers.2346864.n4.nabble.com/Move-documentation-from-readme-io-to-GitHub-pages-td16409.html Add to the JIRA ticket as a watcher if

[GitHub] ignite pull request #3612: Ignite 2.3.2.b3

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3612 Ignite 2.3.2.b3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.3.2.b3 Alternatively you can review and

RE: Is ML a part of the Ignite.C# API? eom

… the reason I ask being that ML is included in the Ignite diagram in the Ignite.C# documentation page, but there is no documentation section for it. *From:* Raymond Wilson [mailto:raymond_wil...@trimble.com] *Sent:* Wednesday, March 7, 2018 3:55 PM *To:* u...@ignite.apache.org *Cc:*

Re: Ignite contibutors page

I'm not mentioned in this list too. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Ignite contibutors page

+1 -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-7894) Web console: extract new design collapsible panels into component

Ilya Borisov created IGNITE-7894: Summary: Web console: extract new design collapsible panels into component Key: IGNITE-7894 URL: https://issues.apache.org/jira/browse/IGNITE-7894 Project: Ignite

Re: [VOTE] Apache Ignite 2.4.0 RC1

Hello, Vladimir. I'm looked into apache-ignite-hadoop-2.4.0-bin.zip/HADOOP_README.txt It contains: ``` Installation requirements: 1. Windows, Linux, or MacOS environment. 2. Java 7 or 8 (latest update is advisable). ``` Seems, it has to be updated because Java 7 is not supported in 2.4 В

Re: [VOTE] Apache Ignite 2.4.0 RC1

Nikolai, please file a ticket for this for 2.5 version. I doubt its a blocker for this release. D. On Tue, Mar 6, 2018 at 8:41 PM, Nikolay Izhikov wrote: > DEVNOTEX.txt also contains mentioning of jdk7: > > ``` > Ignite Hadoop Accelerator Maven Build Instructions > ... >

[jira] [Created] (IGNITE-7896) Files of evicted partitions do not removed from disk storage

Vladislav Pyatkov created IGNITE-7896: - Summary: Files of evicted partitions do not removed from disk storage Key: IGNITE-7896 URL: https://issues.apache.org/jira/browse/IGNITE-7896 Project:

[jira] [Created] (IGNITE-7895) Revise unit tests for Web Console.

Alexander Kalinin created IGNITE-7895: - Summary: Revise unit tests for Web Console. Key: IGNITE-7895 URL: https://issues.apache.org/jira/browse/IGNITE-7895 Project: Ignite Issue Type:

Re: checksum file Release Distribution Policy

http://apache.org/dist/ignite/2.3.0/ > On 6 Mar 2018, at 23:21, Dmitriy Setrakyan wrote: > > I don't see MD5 files anywhere on the website: > https://ignite.apache.org/download.cgi > > Where do we have them? > > D. > > > On

Re: Stop nodes after test by default - IGNITE-6842

Hi Maxim, are there any news on these test fails? Is issue ready for review? Sincerely, Dmitiry Pavlov вт, 27 февр. 2018 г. в 17:12, Dmitry Pavlov : > Hi, thank you! > > I've found several suspicious fails: such test fails have rate less than > 1%, it is probably new

Re: Stop nodes after test by default - IGNITE-6842

Hello Dmitry, Yes, I've updated test classes as you metioned before. Now i'm fixing review comments. Within next few days I'll prepare final version of this PR. вт, 6 мар. 2018 г. в 20:12, Dmitry Pavlov : > Hi Maxim, > > are there any news on these test fails? > > Is

Re: Thin client: transactions support

Hi Dmitriy. I don't think we have a design proposal for transaction support in thin clients. Do you mind taking this initiative and creating an IEP on Wiki? D. On Tue, Mar 6, 2018 at 8:46 AM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Hi, Igniters. > > I've seen a lot of

[GitHub] ignite pull request #3611: Ignite 7751

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

Re: Stop nodes after test by default - IGNITE-6842

Ok, thank you. Please let me know when we can proceed with review https://reviews.ignite.apache.org/ignite/review/IGNT-CR-502 вт, 6 мар. 2018 г. в 20:17, Maxim Muzafarov : > Hello Dmitry, > > Yes, I've updated test classes as you metioned before. > Now i'm fixing review

Re: Data compression design proposal

Hi, I guess page level compression make sense on page loading / eviction. In this case we can decrease I/O operation and performance boost can be reached. What is goal for in-memory compression? Holds about 2-5x data in memory with performance drop? Also please clarify the case with

Re: MTCGA: Tests of the week

Great work! Best Regards, Igor On Tue, Mar 6, 2018 at 1:42 AM, Denis Magda wrote: > Astonishing progress! Thanks for keep driving this activity and making the > project more and more reliable. > > -- > Denis > > On Mon, Mar 5, 2018 at 1:47 PM, Dmitry Pavlov

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hello, Alexey. Thank you for very helpfull feedback. We certainly consider all the issues you written. > How encryption keys will be stored and accessed? *MEK(Master encryption key)* will be stored in regular java key store JKS [1]. To access it admin must enter key store password. *CEK(Cache

[GitHub] ignite pull request #3606: IGNITE-7845 fix checking atomicLong in IgniteClie...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/3606 IGNITE-7845 fix checking atomicLong in IgniteClientDataStructuresTest… …#testAtomicLong. You can merge this pull request into a Git repository by running: $ git pull

Re: Code inspection

Dmitriy, I like this idea a lot. For example, the inspection profile should have inspection 'Anonymous class can be converted to lambda' disabled because quite a lot of such classes can be sent over the network (although even anonymous classes are discourage for such purposes). I believe we can

Re: Transparent Data Encryption (TDE) in Apache Ignite

Alexey, Yes, administrator has to enter password before cluster *activation*(not start). В Вт, 06/03/2018 в 13:27 +0300, Alexey Goncharuk пишет: > Nikolay, > > Does it mean that administrator must enter the MEK password upon Ignite > start? > > 2018-03-06 13:24 GMT+03:00 Nikolay Izhikov

[jira] [Created] (IGNITE-7887) [ML] Adopt SVM Linear Multi-Class Classification Model and Trainer to the new Partitioned Dataset

Aleksey Zinoviev created IGNITE-7887: Summary: [ML] Adopt SVM Linear Multi-Class Classification Model and Trainer to the new Partitioned Dataset Key: IGNITE-7887 URL:

Re: Let's keep Apache Ignite docs up-to-date

Hi, Igniters Missed this discussion +1 for git docs, as far as i can see this approach is used by many projects and it seems to be quite good. On 6 March 2018 at 11:44, Alexey Goncharuk wrote: > Igniters, > > Bumping up this discussion. > > I have recently found

Re: Code inspection

Sonar is powerful, yes, but it’s power in thoroughness. I.e. it does its job well in cases of leisurely post-build analysis. I’d suggest we use it (if we will use it) in the following scenarios: — some basic checks Sonar profile for Blocker bugs (it is fast) — something that cannot be passed

Re: Code inspection

What I can suggest now it is to take XML file with existing as is from previous topic (I remember someone in community already prepared settings) and set up TeamCity Run configuration as part of Run All Basic Tests (per commit basis). If we don’t have XML, I suggest to enable build-in Idea

Re: Code inspection

I was thinking about some quick check, which will automatically require minimum runs. Now, any committer can push changes to the master, which break not only the inspection and style, but even the compilation. If this control would be automatic, it can allow us make codebase better quite fast. But

Re: Code inspection

Can we use also Sonar for codestyle (may be some additional code checks) checks on each PR? вт, 6 мар. 2018 г. в 13:42, Petr Ivanov : > Sonar is powerful, yes, but it’s power in thoroughness. I.e. it does its > job well in cases of leisurely post-build analysis. > > I’d

Re: Code inspection

We can use Sonar as instrument for code analysis and test coverage inspections. > On 6 Mar 2018, at 11:28, Dmitriy Govorukhin > wrote: > > Dmitriy, > > As I understood, preview topic was of static code analysis in general. > In this topic, I want to discuss

Re: Transparent Data Encryption (TDE) in Apache Ignite

My bad, the correct link is https://issues.apache.org/jira/browse/IGNITE-5829 2018-03-06 13:04 GMT+03:00 Alexey Goncharuk : > Guys, > > I think this TDE proposal is not thought through enough yet. Please > consider the following points when writing the IEP: > > * How

Re: Code inspection

Petr, I've heard Sonar is powerful tool. Would it help us to prohibit commits to master w/o test run / too much failed tests / too much inspection errors appeared? вт, 6 мар. 2018 г. в 13:22, Alexey Goncharuk : > Dmitriy, > > I like this idea a lot. For example, the

Re: Transparent Data Encryption (TDE) in Apache Ignite

Nikolay, Does it mean that administrator must enter the MEK password upon Ignite start? 2018-03-06 13:24 GMT+03:00 Nikolay Izhikov : > Hello, Alexey. > > Thank you for very helpfull feedback. > We certainly consider all the issues you written. > > > How encryption keys will

RE: Ignite contibutors page

Hi, I am not mentioned too -Original Message- From: Petr Ivanov [mailto:mr.wei...@gmail.com] Sent: Tuesday, March 6, 2018 4:19 PM To: dev@ignite.apache.org Subject: Re: Ignite contibutors page +1 not mentioned > On 6 Mar 2018, at 15:36, Дмитрий Рябов wrote: >

[jira] [Created] (IGNITE-7891) awaitPartitionMapExchange works incorrectly if partitioned cache has backup

Alexey Kuznetsov created IGNITE-7891: Summary: awaitPartitionMapExchange works incorrectly if partitioned cache has backup Key: IGNITE-7891 URL: https://issues.apache.org/jira/browse/IGNITE-7891

Re: Ignite contibutors page

+1 -- Best regards, Andrey Kuznetsov.

Re: MTCGA: Tests of the week

Great progress, guys! Keep going! --Yakov

[GitHub] ignite pull request #3609: IGNITE-6113 Return back old implementation instea...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3609 IGNITE-6113 Return back old implementation instead of 'removeIf' You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3608: IGNITE-7889: .NET: linq GroupBy and Where does no...

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3608 IGNITE-7889: .NET: linq GroupBy and Where does not work together You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3606: IGNITE-7845 fix checking atomicLong in IgniteClie...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3606 ---

Request for contributor permissions

Hello Ignite Community! My name is Ivan Daschinskiy. I want to contribute to Apache Ignite and want to start with this issue - IGNITE-6860 , my JIRA username *ivandasch*. Any help on this will be appreciated. Thanks a lot! -- Sincerely yours,

Re: Request for contributor permissions

Ivan, Welcome to the community! I've added you to the contributors list. --AG 2018-03-06 16:52 GMT+03:00 Ivan Daschinsky : > Hello Ignite Community! > > My name is Ivan Daschinskiy. I want to contribute to Apache Ignite and want > to start with this issue - IGNITE-6860 >

Re: [VOTE] Apache Ignite 2.4.0 RC1

Alexey, sorry, did not mean to underappreciate anyone's work! Thanks for the explanation. On Tue, Mar 6, 2018 at 11:31 AM, Alexey Kuznetsov wrote: > Pavel, > > Web Console> Fixed output of big numbers in SQL query results > > As one who fix this issue - that one was not

Re: Partition loss policy - how to use?

Hi, Is there any update on this topic? Any tickets created for points mentioned by Valentin? Thanks. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-7892) Remove aquirence of any locks from toString methods

Alexander Belyak created IGNITE-7892: Summary: Remove aquirence of any locks from toString methods Key: IGNITE-7892 URL: https://issues.apache.org/jira/browse/IGNITE-7892 Project: Ignite

[GitHub] ignite pull request #3610: IGNITE-7864 Control utility: Add confirm on dange...

GitHub user macrergate opened a pull request: https://github.com/apache/ignite/pull/3610 IGNITE-7864 Control utility: Add confirm on dangerous operations You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Thin client: transactions support

Hi, Igniters. I've seen a lot of discussions about thin client and binary protocol, but I did not hear anything about transactions support. Do we have some draft for this purpose? As I understand we have several problems: - thread and transaction have hard related (we use thread-local

Re: Ignite nightly build job on Apache Jenkins server

I guess there is no such thing as Nightly RELEASE Builds right now in TeamCity. We have only nightly test builds on master. I guess there is not much effort in adding nightly release build, so, if this task has it’s priority — please fill the ticket and I’ll prepare corresponding build. >

Code inspection

Hi folks, Do we have 'inspection' [1] scheme for ignite? I see a lot of warnings in my code, and I guess it is because everyone uses different schemes. Let's start the discussion. [1] IDEA inspection

Re: Code inspection

Hi Dmitriy, I think we should resurrect thread about addition of code inspections, and later we can enable automatic control step to TeamCity. Could you help me to find it? вт, 6 мар. 2018 г. в 11:11, Dmitriy Govorukhin : > Hi folks, > > Do we have 'inspection'

Re: Ignite nightly build job on Apache Jenkins server

Amount of effort will exceed creating new build on TeamCity. Currently on TeamCity we have prepared and working Release Build project, which can be copied and modified to run at night. A think we have to discuss the delivery of those nightly release artifacts to users: some king of page

[GitHub] ignite pull request #3604: ignite-6643-2.1Marshalling improvements (backport...

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/3604 ---

Re: [VOTE] Apache Ignite 2.4.0 RC1

Pavel, Web Console> Fixed output of big numbers in SQL query results As one who fix this issue - that one was not so *trivial* :). On Tue, Mar 6, 2018 at 3:05 PM, Vladimir Ozerov wrote: > Pavel, > > There is no changes in Ignite C++. As far as Web Console fix, I would

Re: [VOTE] Apache Ignite 2.4.0 RC1

Pavel, There is no changes in Ignite C++. As far as Web Console fix, I would not say it is trivial because it affected UX, so IMO it is important to notify users about the fix. On Tue, Mar 6, 2018 at 10:30 AM, Pavel Tupitsyn wrote: > Regarding release notes: > > 1. No

Re: Ignite nightly build job on Apache Jenkins server

On Tue, Mar 6, 2018 at 12:02 AM, Petr Ivanov wrote: > I guess there is no such thing as Nightly RELEASE Builds right now in > TeamCity. > > We have only nightly test builds on master. > > I guess there is not much effort in adding nightly release build, so, if > this task

[GitHub] ignite pull request #3321: Ignite-2.4-java9

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/3321 ---

Re: Ignite nightly build job on Apache Jenkins server

IMO we should migrate to one platform instead of fixing deprecated. Now target platform is TeamCity. вт, 6 мар. 2018 г. в 11:06, Dmitriy Setrakyan : > On Tue, Mar 6, 2018 at 12:02 AM, Petr Ivanov wrote: > > > I guess there is no such thing as Nightly

Re: Code inspection

Dmitriy, As I understood, preview topic was of static code analysis in general. In this topic, I want to discuss only idea inspection rule. In future, of course, we can expаnd this rule to the TeamCity build. On Tue, Mar 6, 2018 at 11:16 AM, Nikolay Izhikov wrote: > Hello,

Re: Code inspection

Hello, Igniters. +1 to automatic code style tools. Let's make it already! Do we have a ticket for it? Related discussion - http://apache-ignite-developers.2346864.n4.nabble.com/Static-code-analysis-for-Java-td22195.html В Вт, 06/03/2018 в 08:15 +, Dmitry Pavlov пишет: > Hi Dmitriy, > > I

[GitHub] ignite pull request #3313: Ignite-2.4-java8

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/3313 ---

[GitHub] ignite pull request #3605: ignite-6643-2.3 Marshalling improvements

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/3605 ---

Re: Let's keep Apache Ignite docs up-to-date

Igniters, Bumping up this discussion. I have recently found out that we have this process for documenting new releases [1] which looks quite ridiculous to me. First, creating a copy of page with next-version suffix is inconvenient and error-prone: the next-version page is not visible to anyone,

Re: Ignite contibutors page

Hi Igniters! I'm not mentioned too. Dmitriy Ryabov. 2018-03-05 23:39 GMT+03:00 Denis Magda : > Hi Dmitriy, > > Thanks for kicking off the discussion. I'll wait for a couple of days for > other response and update the page in bulk. > > -- > Denis > > On Mon, Mar 5, 2018 at

[jira] [Created] (IGNITE-7888) ODBC: Add support for SQL_ATTR_LOGIN_TIMEOUT

Alexey Popov created IGNITE-7888: Summary: ODBC: Add support for SQL_ATTR_LOGIN_TIMEOUT Key: IGNITE-7888 URL: https://issues.apache.org/jira/browse/IGNITE-7888 Project: Ignite Issue Type:

Re: checksum file Release Distribution Policy

We keep MD5 files for backward compatibility On Tue, Mar 6, 2018 at 3:50 PM, Vladimir Ozerov wrote: > I am not sure. We do have SHA512 files, which is ok. But we also have MD5 > files, which are now "SHOULD NOT" be provided. Is it OK that we still have > them? > > On Tue,

Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts

Yakov, 1. The proposal list of parameters to deprecate: TcpDiscoverySpi.setConnectTimeout (covered by IgniteConfiguration.setFailureDetectionTimeout) TcpDiscoverySpi.setReconnectCount (covered by IgniteConfiguration.setFailureDetectionTimeout) TcpDiscoverySpi.setSocketTimeout (covered by

Re: Ignite contibutors page

+1 not mentioned > On 6 Mar 2018, at 15:36, Дмитрий Рябов wrote: > > Hi Igniters! > > I'm not mentioned too. Dmitriy Ryabov. > > 2018-03-05 23:39 GMT+03:00 Denis Magda : > >> Hi Dmitriy, >> >> Thanks for kicking off the discussion. I'll wait for a

[GitHub] ignite pull request #3445: IGNITE-6113 Async eviction

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3445 ---

[jira] [Created] (IGNITE-7890) Node start with corrupted pds hangs indefinitely.

Ilya Lantukh created IGNITE-7890: Summary: Node start with corrupted pds hangs indefinitely. Key: IGNITE-7890 URL: https://issues.apache.org/jira/browse/IGNITE-7890 Project: Ignite Issue

Re: checksum file Release Distribution Policy

I am not sure. We do have SHA512 files, which is ok. But we also have MD5 files, which are now "SHOULD NOT" be provided. Is it OK that we still have them? On Tue, Mar 6, 2018 at 10:23 AM, Dmitriy Setrakyan wrote: > On Mon, Mar 5, 2018 at 12:57 PM, Denis Magda

Re: Transparent Data Encryption (TDE) in Apache Ignite

Guys, I think this TDE proposal is not thought through enough yet. Please consider the following points when writing the IEP: * How encryption keys will be stored and accessed? If the encryption key is stored with the same permissions as the main data storage, the whole exercise with encryption

[GitHub] ignite pull request #3607: IGNITE-7876

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3607 IGNITE-7876 * Removed Multiclass-classification related code * Fixed tests * Adopted Model and Trainer You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-7889) .NET: linq GroupBy and Where does not work together.

Alexey Popov created IGNITE-7889: Summary: .NET: linq GroupBy and Where does not work together. Key: IGNITE-7889 URL: https://issues.apache.org/jira/browse/IGNITE-7889 Project: Ignite Issue