Re: New API docs look for Ignite.NET

2017-09-05 Thread Sergey Kozlov
Pavel

I like the idea to change Doxygen. It really becomes uncomfortable to
regenerate often.
Do you know how much DocFX faster than Doxygen (if you already tried that)?



On Tue, Sep 5, 2017 at 11:16 AM, Pavel Tupitsyn 
wrote:

> Igniters and users,
>
> Historically we've been using Doxygen [1] to generate .NET API
> documentation [2].
>
> Recently it became very slow on our code base (more than 30 minutes to
> generate), and I could not find any solution or tweak to fix that. Other
> issues include outdated looks and limited customization possibilities.
>
> I propose to replace it with DocFX [3] [4]:
> - Popular .NET Foundation project
> - Good looks and usability out of the box
> - Easy to set up
>
> Our docs will look like this: [5]
> Let me know if you have any objections or suggestions.
>
> Pavel
>
>
> [1] http://www.stack.nl/~dimitri/doxygen/
> [2] https://ignite.apache.org/releases/latest/dotnetdoc/index.html
> [3] https://dotnet.github.io/docfx/
> [4] https://issues.apache.org/jira/browse/IGNITE-6253
> [5] https://ptupitsyn.github.io/docfx-test/api/index.html
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com


Re: Testing Ignite Applications Locally

2017-08-28 Thread Sergey Kozlov
Yakov, ok. I'll do that

On Mon, Aug 28, 2017 at 6:19 PM, Yakov Zhdanov  wrote:

> >As far as Maven archetype, Yakov, is the only purpose of it to load a
> project, so users can add tests to it?
>
> Yes, but not just add. We will also be providing test examples, data
> loading application sample, shell scripts, etc. This can be pretty handy
> thing to create project with all dependencies initialized and useful stuff.
>
> --Yakov
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com


Re: Testing Ignite Applications Locally

2017-08-26 Thread Sergey Kozlov
The idea is great!

Also I would suggest an ability to run new (modified) tests 100 times in
loop on the CI server to make sure that they don't cause no sporadic
failures (we can include that as part of the requirements before review)

On Sat, Aug 26, 2017 at 6:16 PM, Dmitriy Setrakyan 
wrote:

> Love the idea. Let's add Testing Ignite Apps page on Readme. Denis, I
> don't think we need many snippets, just a few.
>
> As far as Maven archetype, Yakov, is the only purpose of it to load a
> project, so users can add tests to it?
>
> D.
>
> On Fri, Aug 25, 2017 at 8:51 AM, Denis Magda  wrote:
>
>> Yasha,
>>
>> Sure, I’ll help from the documentation point but will need raw material
>> from you, guys - test snippets, essential configuration parameters, etc.
>>
>> —
>> Denis
>>
>> On Aug 25, 2017, at 8:30 AM, Yakov Zhdanov  wrote:
>>
>> Guys,
>>
>> I want to discuss the subject again. It is pretty vivid that having wide
>> set of local unit and simple integration tests most likely help to avoid
>> many failures and bugs when going to server environment.
>>
>> I participated in many POC and I can say for sure - if developers are not
>> implementing local tests then their application is broken. This is true for
>> the entire industry. Why does anyone think that Ignite and distributed
>> systems in general are exceptions here? Complexity added by distributed
>> nature probably needs local tests even more.
>>
>> So, what Ignite already offers here and what can be done further?
>>
>> 1. Ignite offers ability to emulate cluster and even many cluster in a
>> single VM. Let's create a page on readme.io explaining how to start
>> topologies in a single VM and provide couple examples of unit tests for
>> cache operations and, for example, queries. Denis Magda, can you help?
>> (Yes, we don't have the page explaining how to test Ignite locally!)
>>
>> 2. Ignite has a large and rich set of tests in its code base. We can
>> provide the link on the page at p1.
>>
>> 3. Let's create maven archetype for Ignite. So, executing the command [1]
>> will bring me inited project with valid poms, sample batch scripts, sample
>> Ignite configs, sample logger configuration and test sources folder
>> containing several JUnits (!!).
>>
>> [1]  mvn archetype:generate \
>>   -DinteractiveMode=false \
>>   -DarchetypeGroupId=org.apache.ignite \
>>   -DarchetypeArtifactId=ignite-app-archetype \
>>   -DgroupId=org.sample \
>>   -DartifactId=sampleapp \
>>   -Dversion=1.0
>>
>> Please share your thoughts and we can file tickets to start moving.
>>
>> --Yakov
>>
>>
>>
>


-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com


Re: Apache Ignite Site Changed its Face

2017-07-28 Thread Sergey Kozlov
Looks like we're *going over the dark side* :-)

On Fri, Jul 28, 2017 at 11:17 AM, Pavel Tupitsyn 
wrote:

> Looks great on desktop, but on mobile it is a disaster :(
>
> http://imgur.com/a/VIT1B
>
>
>
> On Fri, Jul 28, 2017 at 11:05 AM, Yakov Zhdanov 
> wrote:
>
>> I like the new design. Looks good!
>>
>> --Yakov
>>
>
>


-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com


Re: Can ignite-spark support spark 1.6.x?

2016-12-02 Thread Sergey Kozlov
Hi Kaiming

At leat hadoop edition of Apache Ignite can be compiled against Apache
Spark 1.5.2 and 1.6.3


On Fri, Dec 2, 2016 at 7:58 AM, Kaiming Wan <344277...@qq.com> wrote:

> hi,
>
> I have found that ignite-spark-1.7.0 doesn't support spark 2.0.x.
>  Does
> it support spark 1.6.x?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Can-ignite-spark-support-spark-1-6-x-tp9358.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com


Re: Is it possible to enable both REPLICATED and PARTITIONED?

2016-10-10 Thread Sergey Kozlov
Hi, Tracyl.

Cache mode (REPLICATED or PARTITIONED) is a cache configuration property
and you can have the different caches with different cache modes at the
same time on the running grid.

On Mon, Oct 10, 2016 at 9:02 AM, Alexey Kuznetsov 
wrote:

> Hi, Tracyl.
>
> Actually, REPLICATED cache is a PARTITIONED cache win backups on all nodes.
>
> But, why did you need  this?
>
> On Mon, Oct 10, 2016 at 10:46 AM, Tracyl  wrote:
>
>> As subject shows.
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Is-it-possible-to-enable-both-REPLICATED-
>> and-PARTITIONED-tp8167.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> Alexey Kuznetsov
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com


Re: Ignite Download links broken

2016-06-19 Thread Sergey Kozlov
Hi

It's a known issue: apache site puts links to a nearest site for user (I
suppose it based on IP address) and does it incorrect.

On Mon, Jun 20, 2016 at 8:37 AM, Dmitriy Setrakyan 
wrote:

> Worked for me just now. Can you try again?
>
> On Sun, Jun 19, 2016 at 2:59 AM, Christos Erotocritou <
> chris...@gridgain.com> wrote:
>
>> Hey guys,
>>
>> The links on the website seem to be broken, can someone check this?
>>
>> https://ignite.apache.org/download.html#binaries <
>> https://ignite.apache.org/download.html#binaries>
>>
>> Thanks,
>>
>> Christos
>
>
>


-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com


Re: Ignite - rest api port

2016-06-03 Thread Sergey Kozlov
Hi

You should copy directory named *ignite-rest-http* from *libs/optional/* to
*libs/* and restart node

On Fri, Jun 3, 2016 at 9:08 PM, M Singh  wrote:

> Hi Folks:
>
> I have downloaded the apache-ignite-fabric-1.6.0-bin.zip file an have
> started it with the ignite.sh script.
>
> However, I am not able to connect to the rest service url (
> http://localhost:8080/ignite?cmd=version) - it returns an empty
> response.  I think that rest service is running on another port, but I am
> not sure how to find it/change it.
>
> The ignite.sh -h also did not give me any info about it.  Perhaps this
> info is in one of the xml type.
>
> Please let me know if anyone has any pointers for me.
>
> Thanks
>
>
>
>
>
>
>


-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com


Re: ignite service session issue

2016-04-23 Thread Sergey Kozlov
Hi

You should use nohup command which prevents closing application after log
out
Please take a look
http://stackoverflow.com/questions/285015/linux-prevent-a-background-process-from-being-stopped-after-closing-ssh-client

On Sat, Apr 23, 2016 at 7:05 AM, Zhengqingzheng 
wrote:

> Hi there,
>
> I am running the ignite service via ssh terminal.
>
> I use command like this : ./ignite.sh  –J-Xms8g –J-Xmx8g  &
>
> However, when I turn off the terminal, the ignite server is also closed.
>
> Is there anyway to make sure the service running without depend on
> terminal session?
>
>
>
> Cheers,
>
> Kevin
>
>
>
> *[image: logo]**郑清正**Kevin Zheng| Research Engineer*
>
> 华为软件技术有限公司Huawei Software Technologies Co.,Ltd. | 电信软件技术规划部Technology
> Planning Dept,CS
>
> (Phone) 025-56620168 | (Mobile)17072565656 | (Fax) 025-56623561
>
> 南京市软件大道101号华为基地N4-3F-A190S 邮编:210012|HUAWEI Area N4-3F-A190S, Software
> Ave., Yuhuatai District,Nanjing 210012, P.R.China
>
> [image: cid:image002.png@01CF9D2E.4FBF0950]
>
>
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com