[jira] [Created] (IGNITE-10846) Improve docs for "Disabling WAL Archiving"

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-10846:


 Summary: Improve docs for "Disabling WAL Archiving"
 Key: IGNITE-10846
 URL: https://issues.apache.org/jira/browse/IGNITE-10846
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Prachi Garg
Assignee: Prachi Garg
 Fix For: 2.8


Provide pros and cons of disabling WAL Archiving.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Packt wants to feature books

[Prachi Garg]

Hi,

I've added a link to the book under the Docs menu item on the website.

On Tue, Dec 11, 2018 at 10:41 AM Denis Magda  wrote:

> Hello Hishit,
>
> Thanks for sharing the news, great!
>
> Prachi, could you please add a reference to the to our website menu?
>
> --
> Denis
>
> On Tue, Dec 11, 2018 at 10:14 AM Nishit Rajput 
> wrote:
>
>> Hi team,
>>
>>
>> I am Nishit from Packt. We publish over 50 books related to trending and
>> upcoming technologies every month. We also feature various books on Project
>> websites.
>>
>>
>> We would be interested in featuring our recently published book Apache
>> Ignite Quick Start Guide<
>> https://www.packtpub.com/big-data-and-business-intelligence/apache-ignite-quick-start-guide>
>> by Sujoy Acharya
>>
>>
>> The book takes you through the basics of Apache Ignite and in-memory
>> technologies. You will learn about installation and clustering Ignite
>> nodes, caching topologies, and various caching strategies, such as cache
>> aside, read and write through, and write behind. Next, you will delve into
>> detailed aspects of Ignite’s data grid: web session clustering and querying
>> data.
>>
>> You will learn how to process large volumes of data using compute grid
>> and Ignite’s map-reduce and executor service. You will learn about the
>> memory architecture of Apache Ignite and monitoring memory and caches. You
>> will use Ignite for complex event processing, event streaming, and the
>> time-series predictions of opportunities and threats. Additionally, you
>> will go through off-heap and on-heap caching, swapping, and native and
>> Spring framework integration with Apache Ignite.
>>
>> By the end of this book, you will be confident with all the features of
>> Apache Ignite 2.x that can be used to build a high-performance system
>> architecture.
>>
>>
>> We can shorten the description as per your website's requirement.
>>
>>
>> I am certain this book will prove to be an insightful resource to the
>> developers.
>>
>>
>> Do let me know if we can feature this book on your website and if you can
>> help us featuring it. If not, can you please direct me to the right person
>> for this requirement.
>>
>>
>> Looking forward to your reply.
>>
>>
>> Thanks and regards,
>>
>> [https://s3-eu-west-1.amazonaws.com/email-signature-packt/128x128px.png]
>>
>>
>>
>>
>>
>> Nishit Rajput
>>
>> Author Marketing Executive
>>
>>
>>
>>  [https://s3-eu-west-1.amazonaws.com/email-signature-packt/ph.png]
>>  022-28328148
>>
>>  [https://s3-eu-west-1.amazonaws.com/email-signature-packt/web.png]
>> www.packt.com
>>  [https://s3-eu-west-1.amazonaws.com/email-signature-packt/msg.png]
>> nish...@packt.com
>> [https://s3-eu-west-1.amazonaws.com/email-signature-packt/loc.png]  Plot
>> No.103, Arena House, 3rd Floor,12th Road, MIDC, Andheri (E), Mumbai -
>> 400093 Mumbai .
>>
>>
>> [https://www.facebook.com/PacktPub/?ref=br_rs]<
>> https://www.facebook.com/PacktPub/?ref=br_rs>  [
>> https://twitter.com/PacktPub]    [
>> https://www.linkedin.com/company/packt-publishing/] <
>> https://www.linkedin.com/company/packt-publishing/>   [
>> https://www.youtube.com/channel/UC3VydBGBl132baPCLeDspMQ] <
>> https://www.youtube.com/channel/UC3VydBGBl132baPCLeDspMQ>
>>
>>
>>
>>
>>
>>
>>
>> Packt Publishing Private Limited. Registered Address: Plot No.103, Arena
>> House, 3rd Floor,12th Road, MIDC, Andheri (E), Mumbai - 400093.
>> CIN:U22100MH2005PTC152766
>> This E-mail is confidential. It may also be legally privileged. If you
>> are not the addressee you may not copy, forward, disclose or use any part
>> of it. If you have received this message in error, please delete it and all
>> copies from your system and notify the sender immediately by return E-mail.
>> Whilst Packt Publishing Ltd take every reasonable precaution to avoid the
>> transfer of software viruses or defects that may cause damage to computer
>> systems; it is the responsibility of the recipient to ensure that all
>> emails and attachments received are free from infection.
>> The word 'Packt'® and the Packt logo are registered trademarks which
>> belong to Packt Publishing Limited.
>>
>

Re: [Fwd: Returned post for annou...@apache.org]

[Prachi Garg]

For point 3, I cannot find where  dist.apache.org is used...Can you please
point me to the right place?

On Thu, Dec 13, 2018 at 6:07 AM Peter Ivanov  wrote:

> ASC / SHA512 verification:
>
> 1. Download signing key: wget -c https://www.apache.org/dist/ignite/KEYS
> 2. Import key: gpg --import KEYS
> 3. Download release with signature and sha512 hash sum: wget -c
> http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip
> http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip.asc
> http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip.sha512
> 4. Verify ASC signature: gpg --verify apache-ignite-2.7.0-src.zip.asc
> apache-ignite-2.7.0-src.zip
> 5. Verify SHA512 hash sum: sha512sum -c apache-ignite-2.7.0-src.zip.sha512
>
>
>
>
> On 10 Dec 2018, at 22:45, Denis Magda  wrote:
>
> Forwarding to the dev list.
>
> *Prachi*, could you please help us with 3-5? It requires minor updates on
> the webpage.
>
> *Sergey K.*, *Peter*, could you assist with 1 and 2?
>
> --
> Denis
>
> On Fri, Dec 7, 2018 at 11:19 PM Nikolay Izhikov 
> wrote:
>
>> Hello, Igniters.
>>
>> Seems that our download page doesn't meet apache requirements.
>> I think we should update the page according to apache rules.
>>
>> Who can do it?
>>
>>
>>
>> -- Forwarded message --
>> From: announce-ow...@apache.org
>> To: nizhi...@apache.org
>> Cc:
>> Bcc:
>> Date: 6 Dec 2018 13:02:57 -
>> Subject: Returned post for annou...@apache.org
>>
>> Hi! This is the ezmlm program. I'm managing the
>> annou...@apache.org mailing list.
>>
>> I'm sorry, your message (enclosed) was not accepted by the moderator.
>> If the moderator has made any comments, they are shown below.
>>
>> >  >
>> Sorry, but the download page does not meet requirements.
>>
>> 1) There is no link to the KEYS file
>> https://www.apache.org/dist/ignite/KEYS
>> This is necessary for validating downloaded artifacts
>>
>> 2) No description of how to validate downloads
>>
>> 3) There are links to dist.apache.org - that host is only intended for
>> use
>> during release preparation and publication.
>> Use https://www.apache.org/dist/ignite/.
>> .. instead.
>>
>> 4) There is a link to nightly builds.
>> That is not allowed on a public download page, as the builds have not been
>> voted on.
>>
>> 5) The paragraph introducing the binary artifact says:
>>
>> "In order to verify the release, we recommend that you download the
>> official source distribution and verify the signatures of the downloaded
>> files before opening them."
>>
>> This does not make sense in the binary section (it belongs in the source
>> section and/or needs rewording).
>> Nor is there any description of how to perform the verification.
>>
>> Please correct the page and resubmit the announce when that has been done.
>>
>> Sebb
>> <  <
>>
>>
>>
>>
>> -- Forwarded message --
>> From: Nikolay Izhikov 
>> To: annou...@apache.org
>> Cc:
>> Bcc:
>> Date: Thu, 6 Dec 2018 15:02:21 +0300
>> Subject: Fwd: [ANNOUNCE] Apache Ignite 2.7.0 Released
>> The Apache Ignite Community is pleased to announce the release of
>> Apache Ignite 2.7.0.
>>
>> Apache Ignite [1] is a memory-centric distributed database, caching,
>> and processing platform for transactional, analytical, and streaming
>> workloads delivering in-memory speeds at petabyte scale.
>>
>> This release introduce several major features and fixes some critical
>> issues
>> https://ignite.apache.org/releases/2.7.0/release_notes.html
>>
>> Download the latest Ignite version from here:
>> https://ignite.apache.org/download.cgi
>>
>> Please let us know [2] if you encounter any problems.
>>
>> Regards,
>> Nikolay Izhikov on behalf of Apache Ignite community
>>
>> [1] https://ignite.apache.org
>> [2] https://ignite.apache.org/community/resources.html#ask
>>
>
>

Re: [Fwd: Returned post for annou...@apache.org]

[Prachi Garg]

Ok, I'll fix issues 3-5.

On Mon, Dec 10, 2018 at 11:44 AM Denis Magda  wrote:

> Forwarding to the dev list.
>
> *Prachi*, could you please help us with 3-5? It requires minor updates on
> the webpage.
>
> *Sergey K.*, *Peter*, could you assist with 1 and 2?
>
> --
> Denis
>
> On Fri, Dec 7, 2018 at 11:19 PM Nikolay Izhikov 
> wrote:
>
> > Hello, Igniters.
> >
> > Seems that our download page doesn't meet apache requirements.
> > I think we should update the page according to apache rules.
> >
> > Who can do it?
> >
> >
> >
> > -- Forwarded message --
> > From: announce-ow...@apache.org
> > To: nizhi...@apache.org
> > Cc:
> > Bcc:
> > Date: 6 Dec 2018 13:02:57 -
> > Subject: Returned post for annou...@apache.org
> >
> > Hi! This is the ezmlm program. I'm managing the
> > annou...@apache.org mailing list.
> >
> > I'm sorry, your message (enclosed) was not accepted by the moderator.
> > If the moderator has made any comments, they are shown below.
> >
> > >  >
> > Sorry, but the download page does not meet requirements.
> >
> > 1) There is no link to the KEYS file
> > https://www.apache.org/dist/ignite/KEYS
> > This is necessary for validating downloaded artifacts
> >
> > 2) No description of how to validate downloads
> >
> > 3) There are links to dist.apache.org - that host is only intended for
> use
> > during release preparation and publication.
> > Use https://www.apache.org/dist/ignite/... instead.
> >
> > 4) There is a link to nightly builds.
> > That is not allowed on a public download page, as the builds have not
> been
> > voted on.
> >
> > 5) The paragraph introducing the binary artifact says:
> >
> > "In order to verify the release, we recommend that you download the
> > official source distribution and verify the signatures of the downloaded
> > files before opening them."
> >
> > This does not make sense in the binary section (it belongs in the source
> > section and/or needs rewording).
> > Nor is there any description of how to perform the verification.
> >
> > Please correct the page and resubmit the announce when that has been
> done.
> >
> > Sebb
> > <  <
> >
> >
> >
> >
> > -- Forwarded message --
> > From: Nikolay Izhikov 
> > To: annou...@apache.org
> > Cc:
> > Bcc:
> > Date: Thu, 6 Dec 2018 15:02:21 +0300
> > Subject: Fwd: [ANNOUNCE] Apache Ignite 2.7.0 Released
> > The Apache Ignite Community is pleased to announce the release of
> > Apache Ignite 2.7.0.
> >
> > Apache Ignite [1] is a memory-centric distributed database, caching,
> > and processing platform for transactional, analytical, and streaming
> > workloads delivering in-memory speeds at petabyte scale.
> >
> > This release introduce several major features and fixes some critical
> > issues
> > https://ignite.apache.org/releases/2.7.0/release_notes.html
> >
> > Download the latest Ignite version from here:
> > https://ignite.apache.org/download.cgi
> >
> > Please let us know [2] if you encounter any problems.
> >
> > Regards,
> > Nikolay Izhikov on behalf of Apache Ignite community
> >
> > [1] https://ignite.apache.org
> > [2] https://ignite.apache.org/community/resources.html#ask
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.7.0 Release (RC2)

[Prachi Garg]

Hello Igniters,

The documentation for Apache Ignite 2.7.0 is now public on readme.io
.

-Prachi

On Wed, Dec 5, 2018 at 9:35 AM Nikolay Izhikov  wrote:

> Yes, Denis.
>
> I will do my best to complete release steps today.
> The only things that blocks me is bintray permissions.
> They required to upload rpm and deb packages to corresponding repository.
>
> I've created ticket to the INFRA [1]
> Seems, they, resolve it eventually.
>
> We discussed this issue with other Igniters and decided to do release
> without rpm and deb. When I got permissions, I release them too.
>
> [1] https://issues.apache.org/jira/browse/INFRA-17354
>
> ср, 5 дек. 2018 г., 20:25 Denis Magda dma...@apache.org:
>
> > When are going to complete the post-release steps and announce the
> release?
> > Once the binaries are available on the website we need to release the
> docs.
> >
> >
> > I'm ready to prepare a blog post for blogs.apache.org.
> >
> > --
> > Denis
> >
> > On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov 
> > wrote:
> >
> > > Sorry, Alex.
> > >
> > > I miss your +1.
> > > Thank you, very much for checking RC artifacts.
> > >
> > > вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov akuznet...@apache.org:
> > >
> > > > Nikolay,
> > > >
> > > > Actually 4 "+1"  binding.
> > > >
> > > > You did not count my "+1".
> > > >
> > > > :)
> > > >
> > > >
> > > > On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov 
> > > > wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > > Apache Ignite 2.7.0 release (RC2) has been accepted.
> > > > >
> > > > > 3 "+1" binding votes received:
> > > > >
> > > > > - Pavel Tupitsyn
> > > > > - Dmitriy Pavlov
> > > > > - Nikolay Izhikov
> > > > >
> > > > > Vote thread:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html
> > > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > >
> > >
> >
>

[jira] [Created] (IGNITE-10012) Add Transactional SQL feature description to Ignite website

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-10012:


 Summary: Add Transactional SQL feature description to Ignite 
website
 Key: IGNITE-10012
 URL: https://issues.apache.org/jira/browse/IGNITE-10012
 Project: Ignite
  Issue Type: Task
Reporter: Prachi Garg
Assignee: Prachi Garg
 Fix For: 2.7


[~Artem Budnikov], Please provide some information/ link to the documentation 
about this feature so that some description can be added to the website.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Python thin client installation instructions

[Prachi Garg]

Yes, I will mention the prerequisites.

-Prachi

> On Sep 21, 2018, at 5:18 PM, Denis Magda  wrote:
> 
> I would add a disclaimer or a prerequisite step. That what other companies
> do if a user needs to do some basic installation steps. At least mention it.
> 
> --
> Denis
> 
>> On Fri, Sep 21, 2018 at 3:04 PM Prachi Garg  wrote:
>> 
>> Hi Dmitry,
>> 
>> Thank you for taking the time to explain me everything in such detail :)
>> 
>> I am trying to do this because I have to document. In general, I am
>> assuming that a Python thin client user would already have Python installed
>> and be using it. So, I would not suggest adding any disclaimers regarding
>> Python installation.
>> 
>> The example works with python3 command :)
>> 
>> 
>> -P
>> 
>> 
>> 
>> On Thu, Sep 20, 2018 at 8:31 PM, Dmitry Melnichuk <
>> dmitry.melnic...@nobitlost.com> wrote:
>> 
>>> Prachi,
>>> 
>>> I feel your struggle. It is easier for end user to perceive Python 2 and
>>> Python 3 as different languages, not as versions of one language. They
>>> usually installed alongside each other; their updates are handled
>>> separately. On most systems they have their respective shell commands:
>>> `python2` and `python3`.
>>> 
>>> Shell command `python` can be viewed as an alias of either `python2` or
>>> `python3`. I use an Arch Linux derivative, where `python` is `python3`.
>>> Most other GNU/Linux OSes use `python` as an alias of `python2`. I am not
>>> sure about MacOS. On Windows the latest Python distribution installed
>>> overrule PATH environment variables, so it impossible to predict the
>>> “default” Python version (2 or 3).
>>> 
>>> Luckily, virtualenv was introduced to leverage all these issues. It is
>>> able to handle multiple isolated Python environments, where the `python`
>>> command is set upon the creation of the environment, while the
>>> environment-specific package dependencies are handled transparently with
>>> pip.
>>> 
>>> But the use of pyignite should not be limited to virtualenv. There are
>>> many cases when the use of virtualenv is discouraged or even impossible.
>>> For example, when deploying Python app into an OS-level container or
>>> similar isolating environment, virtualenv would be just a useless
>> overhead.
>>> There are also non-standard Python distributions (used mostly on Windows)
>>> that do not support virtualenv.
>>> 
>>> I am sorry, that users who are not proficient in Python can have so many
>>> problems with following my documentation. But still it seems obvious for
>>> me, that all the details of organizing user's own Python environment are
>>> out of pyignite documentation's scope. The only thing I can suggest to
>>> improve my documentation in this regard is putting a big bold foreword
>> like
>>> this:
>>> 
>>>  It is assumed in this document that you know how to install
>>>  and use Python 3 on your system. Please consult your OS manual pages
>>>  or documentations of your specific Python 3 distribution regarding
>>>  the details of organizing your Python 3 environment. The use of
>>>  virualenv for development with pyignite is highly recommended.
>>> 
>>> But, frankly, I have not seen such disclaimers in the wild and not sure
>> if
>>> it would be useful. It is very vague and do not cover any of the
>> potential
>>> pitfalls.
>>> 
>>> I am sorry for giving such a lengthy explanation here, though I've been
>>> asked a very specific question. I understand you may not have time to
>>> invest in learning virtualenv. If so, you did everything right, just use
>>> `python3` command for launching examples:
>>> 
>>> ```
>>> $ python3 get_and_put.py
>>> ```
>>> 
>>>> On 9/21/18 10:34 AM, Prachi Garg wrote:
>>>> 
>>>> Hi Dmitry,
>>>> 
>>>> Sorry, I am not familiar with Python.
>>>> 
>>>> So there are more issues...
>>>> 
>>>> 1. The version on my mac remains 2.7.10 even though I tried to link to
>>>> the new version.
>>>> 
>>>> ~$ python --version
>>>> Python 2.7.10
>>>> 
>>>> ~$ brew unlink python && brew link --overwrite python3
>>>> Unlinking /usr/local/Cellar/python/3.7.0. <http://3.7.0.>.. 25 symlinks
>>>> removed
>>>

Re: Python thin client installation instructions

[Prachi Garg]

Hi Dmitry,

Thank you for taking the time to explain me everything in such detail :)

I am trying to do this because I have to document. In general, I am
assuming that a Python thin client user would already have Python installed
and be using it. So, I would not suggest adding any disclaimers regarding
Python installation.

The example works with python3 command :)


-P



On Thu, Sep 20, 2018 at 8:31 PM, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:

> Prachi,
>
> I feel your struggle. It is easier for end user to perceive Python 2 and
> Python 3 as different languages, not as versions of one language. They
> usually installed alongside each other; their updates are handled
> separately. On most systems they have their respective shell commands:
> `python2` and `python3`.
>
> Shell command `python` can be viewed as an alias of either `python2` or
> `python3`. I use an Arch Linux derivative, where `python` is `python3`.
> Most other GNU/Linux OSes use `python` as an alias of `python2`. I am not
> sure about MacOS. On Windows the latest Python distribution installed
> overrule PATH environment variables, so it impossible to predict the
> “default” Python version (2 or 3).
>
> Luckily, virtualenv was introduced to leverage all these issues. It is
> able to handle multiple isolated Python environments, where the `python`
> command is set upon the creation of the environment, while the
> environment-specific package dependencies are handled transparently with
> pip.
>
> But the use of pyignite should not be limited to virtualenv. There are
> many cases when the use of virtualenv is discouraged or even impossible.
> For example, when deploying Python app into an OS-level container or
> similar isolating environment, virtualenv would be just a useless overhead.
> There are also non-standard Python distributions (used mostly on Windows)
> that do not support virtualenv.
>
> I am sorry, that users who are not proficient in Python can have so many
> problems with following my documentation. But still it seems obvious for
> me, that all the details of organizing user's own Python environment are
> out of pyignite documentation's scope. The only thing I can suggest to
> improve my documentation in this regard is putting a big bold foreword like
> this:
>
>   It is assumed in this document that you know how to install
>   and use Python 3 on your system. Please consult your OS manual pages
>   or documentations of your specific Python 3 distribution regarding
>   the details of organizing your Python 3 environment. The use of
>   virualenv for development with pyignite is highly recommended.
>
> But, frankly, I have not seen such disclaimers in the wild and not sure if
> it would be useful. It is very vague and do not cover any of the potential
> pitfalls.
>
> I am sorry for giving such a lengthy explanation here, though I've been
> asked a very specific question. I understand you may not have time to
> invest in learning virtualenv. If so, you did everything right, just use
> `python3` command for launching examples:
>
> ```
> $ python3 get_and_put.py
> ```
>
> On 9/21/18 10:34 AM, Prachi Garg wrote:
>
>> Hi Dmitry,
>>
>> Sorry, I am not familiar with Python.
>>
>> So there are more issues...
>>
>> 1. The version on my mac remains 2.7.10 even though I tried to link to
>> the new version.
>>
>> ~$ python --version
>> Python 2.7.10
>>
>> ~$ brew unlink python && brew link --overwrite python3
>> Unlinking /usr/local/Cellar/python/3.7.0. <http://3.7.0.>.. 25 symlinks
>> removed
>> Linking /usr/local/Cellar/python/3.7.0. <http://3.7.0.>.. 25 symlinks
>> created
>>
>> ~$ python --version
>> Python 2.7.10
>>
>> 2. Then I tried to update /pip/, uninstall and re-install /pyignite/
>>
>> ~$ pip install -U pip
>> -bash: /Library/Frameworks/Python.framework/Versions/3.7/bin/pip: No
>> such file or directory
>> ~$ pip3 install -U pip
>> Requirement already up-to-date: pip in /Library/Frameworks/Python.fra
>> mework/Versions/3.7/lib/python3.7/site-packages (18.0)
>>
>> ~$ pip3 uninstall pyignite
>> Uninstalling pyignite-0.3.0:
>>Would remove:
>>  /Library/Frameworks/Python.framework/Versions/3.7/lib/pytho
>> n3.7/site-packages/pyignite-0.3.0.dist-info/*
>>  /Library/Frameworks/Python.framework/Versions/3.7/lib/pytho
>> n3.7/site-packages/pyignite/*
>> Proceed (y/n)? y
>>Successfully uninstalled pyignite-0.3.0
>>
>> ~$ pip3 install pyignite
>> Collecting pyignite
>>Using cached https://files.pythonhosted.org
>> /packages/f1/0f/5669cd63fb37fa20

Re: Python thin client installation instructions

[Prachi Garg]

Hi Dmitry,

Sorry, I am not familiar with Python.

So there are more issues...

1. The version on my mac remains 2.7.10 even though I tried to link to the
new version.

~$ python --version
Python 2.7.10

~$ brew unlink python && brew link --overwrite python3
Unlinking /usr/local/Cellar/python/3.7.0... 25 symlinks removed
Linking /usr/local/Cellar/python/3.7.0... 25 symlinks created

~$ python --version
Python 2.7.10

2. Then I tried to update *pip*, uninstall and re-install *pyignite*

~$ pip install -U pip
-bash: /Library/Frameworks/Python.framework/Versions/3.7/bin/pip: No such
file or directory
~$ pip3 install -U pip
Requirement already up-to-date: pip in
/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages
(18.0)

~$ pip3 uninstall pyignite
Uninstalling pyignite-0.3.0:
  Would remove:

/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/pyignite-0.3.0.dist-info/*

/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/pyignite/*
Proceed (y/n)? y
  Successfully uninstalled pyignite-0.3.0

~$ pip3 install pyignite
Collecting pyignite
  Using cached
https://files.pythonhosted.org/packages/f1/0f/5669cd63fb37fa2025110f61598450567d04a72c8cf5b76bb0ca20c21734/pyignite-0.3.0-py3-none-any.whl
Requirement already satisfied: attrs==18.1.0 in
/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages
(from pyignite) (18.1.0)
Requirement already satisfied: typing==3.6.4 in
/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages
(from pyignite) (3.6.4)
Installing collected packages: pyignite
Successfully installed pyignite-0.3.0


How can I fix this?

On Wed, Sep 19, 2018 at 6:43 PM, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:

> Prachi,
>
> This line in your message
>
> > Requirement already satisfied: pyignite in
> > ./Downloads/ignite-python/modules/platforms/python (0.3.1)
>
> looks like you already did an installation of pyignite in this environment
> before (maybe with "pip install -e ") from
> 'Downloads' folder, then delete or move downloaded copy, and than tried to
> install pyignite again, this time from PyPI ("pip install ").
>
> pip does not work this way. You should either undo the previous install
> ("pip uninstall "), use "--update" argument ("pip install
> --update "), or even better − use virtualenv to create a
> disposable Python environment for every experiment. I provided a link to
> virtualenv manual in the README file and in docs, in the 'Basics → Testing'
> section.
>
> > Also, the installation instruction you have provided are for unix users.
> > What are the installation instructions for Windows users?
>
> I tried to be OS-agnostic in the docs. Please tell me, what part of my
> instructions does not work on Windows.
>
> On 9/20/18 7:32 AM, Prachi Garg wrote:
>
>> Hi Dmitry,
>>
>> I tried to follow the instructions for the Python thin client
>> installation [1].
>>
>> ~$ pip install pyignite
>> Requirement already satisfied: pyignite in 
>> ./Downloads/ignite-python/modules/platforms/python
>> (0.3.1)
>> Requirement already satisfied: typing==3.6.4 in
>> /Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages
>> (from pyignite) (3.6.4)
>> Requirement already satisfied: attrs==18.1.0 in
>> /Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages
>> (from pyignite) (18.1.0)
>>
>> But when I try to run an example, I get an error.
>>
>> ~/Downloads/ignite-python/modules/platforms/python/examples$ python
>> get_and_put.py
>> Traceback (most recent call last):
>>File "get_and_put.py", line 16, in 
>>  from pyignite import Client
>> ImportError: No module named pyignite
>>
>>
>> What else need to be done? I am documenting the instructions on readme.io
>> <http://readme.io>, but I need to be able to run a few examples first.
>>
>> Also, the installation instruction you have provided are for unix users.
>> What are the installation instructions for Windows users?
>>
>> [1] https://apache-ignite-binary-protocol-client.readthedocs.io/
>> en/latest/readme.html#installation
>>
>
>

Python thin client installation instructions

[Prachi Garg]

Hi Dmitry,

I tried to follow the instructions for the Python thin client installation
[1].

~$ pip install pyignite
Requirement already satisfied: pyignite in
./Downloads/ignite-python/modules/platforms/python (0.3.1)
Requirement already satisfied: typing==3.6.4 in
/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages
(from pyignite) (3.6.4)
Requirement already satisfied: attrs==18.1.0 in
/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages
(from pyignite) (18.1.0)

But when I try to run an example, I get an error.

~/Downloads/ignite-python/modules/platforms/python/examples$ python
get_and_put.py
Traceback (most recent call last):
  File "get_and_put.py", line 16, in 
from pyignite import Client
ImportError: No module named pyignite


What else need to be done? I am documenting the instructions on readme.io,
but I need to be able to run a few examples first.

Also, the installation instruction you have provided are for unix users.
What are the installation instructions for Windows users?

[1]
https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/readme.html#installation

Re: Python thin client

[Prachi Garg]

Hi Dmitry,

Not sure if you are aware but all documentation for the thin clients will
be moved to readme.io. Here is the ticket for Python thin clients -
https://issues.apache.org/jira/browse/IGNITE-9522

I am already working on it. So if you make any changes to the docs in your
repo, please let me know so that I don't miss bringing them over to
readme.io

-Prachi

On Tue, Sep 18, 2018 at 4:08 AM, Igor Sapego  wrote:

> Great job.
>
> Best Regards,
> Igor
>
>
> On Tue, Sep 18, 2018 at 11:35 AM Dmitry Melnichuk <
> dmitry.melnic...@nobitlost.com> wrote:
>
> > Igor,
> >
> > All examples are in 'ignite/modules/platforms/python/examples'.
> >
> > I put examples in separate Python files mostly to be able to
> > automatically confirm their operability. All the lengthy explanations
> > and cross-references are in the main documentation:
> >
> >
> > https://apache-ignite-binary-protocol-client.readthedocs.
> io/en/latest/examples.html
> >
> > To make it easier for end users to navigate in pyignite directories, I
> > added a small README file to the 'examples' directory with a short
> > description and a link to the docs:
> >
> >
> > https://github.com/nobitlost/ignite/blob/ignite-7782/
> modules/platforms/python/examples/readme.md
> >
> > If you think this README is lacking something regardless of the main
> > pyignite docs, please let me know.
> >
> > On 9/17/18 8:59 PM, Igor Sapego wrote:
> > > Dmitry,
> > >
> > > Sorry, I was not clear enough. What I mean is that Ignite distributed
> > > by both source and binary releases. Binary releases contain platforms
> > > code, which is needed to write your own application in the language,
> > > but does not contain developer stuff, such as tests, documentation
> > > generating scripts, etc.
> > >
> > > Of course, it is more common to use package managers when
> > > developing your application, and of course, we are going to support
> > > this approach. But still, we provide a way for a user to get any client
> > > without any package manager.
> > >
> > > I like the idea of supplying whl package in a binary release, though it
> > > looks like it's going to take more effort to implement it. But I
> believe
> > > except for the whl package, we will need to supply examples and
> > > instructions, how user can run them.
> > >
> > > What do you think?
> > >
> > > Best Regards,
> > > Igor
> > >
> > >
> > > On Sat, Sep 15, 2018 at 7:03 AM Dmitry Melnichuk <
> > > dmitry.melnic...@nobitlost.com> wrote:
> > >
> > >> Igor,
> > >>
> > >> I am in doubt here because I am not fully comprehend the meaning of
> > >> "binary release". But if it is somehow related to the "distribution"
> > >> thing, I would dare to suggest the following options:
> > >>
> > >> 1. Copy nothing. Just do
> > >>
> > >> ```
> > >> $ python setup.py bdist_wheel
> > >> $ twine upload dist/*
> > >> ```
> > >>
> > >> during the build process (or separately) and let PyPI handle the
> > >> distribution.
> > >>
> > >> This is the most natural and user-friendly way of distributing Python
> > >> packages. End user might only do
> > >>
> > >> ```
> > >> $ pip install pyignite
> > >> ```
> > >>
> > >> as it is suggested by my readme file.
> > >>
> > >> 2. Supply the wheel package. It is the file 'pyignite-*.whl' from
> 'dist'
> > >> directory, that should appear there as the "python setup.py
> bdist_wheel"
> > >> command finishes. Actually, it can be combined with the first option.
> > >>
> > >> The wheel can then be installed by the end user:
> > >>
> > >> ```
> > >> $ pip install pyignite-*.whl
> > >> ```
> > >>
> > >> 3. Supply the following files:
> > >>
> > >> ignite/modules/platforms/python/pyignite/**
> > >> ignite/modules/platforms/python/requirements/**
> > >> ignite/modules/platforms/python/LICENSE
> > >> ignite/modules/platforms/python/README.md
> > >> ignite/modules/platforms/python/setup.py
> > >>
> > >> (** stands for "all the files and sub-folders recursively, starting
> from
> > >> this folder".)
> > >>
> > >> It is not uncommon or wrong to distribute Python programs as text
> > >> without prior packaging, but, in my personal experience, this is a way
> > >> more suitable for one-time scripts or proprietary programs. For
> example,
> > >> most of Python web apps relies on git for deployment, without any
> > >> packaging subsystem.
> > >>
> > >> Here's a few words about wheels:
> > >>
> > >> https://wheel.readthedocs.io/
> > >>
> > >> Here's about uploading to PyPI with twine:
> > >>
> > >>
> > >>
> > https://packaging.python.org/tutorials/packaging-projects/#
> uploading-the-distribution-archives
> > >>
> > >> On 9/14/18 9:05 PM, Igor Sapego wrote:
> > >>> Ok, good.
> > >>>
> > >>> Now, what is about installation? Which directories/files
> > >>> need to be copied to ignite's binary release?
> > >>>
> > >>> Best Regards,
> > >>> Igor
> > >>>
> > >>
> > >
> >
> >
>

Re: PHP thin client

[Prachi Garg]

Hi Stephan, Alexey

That's exactly what readme.io contains - installation instructions,
configuration, and examples for key-value, sql, etc. for thin clients. For
example, see these documentation pages for Node.js (currently hidden in the
latest version of the doc) :

https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client
https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-initialization-and-configuration
https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-key-value
https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-sql
https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-binary-types
https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-security

This how Python and PHP thin clients will also be documented on readme.io

-Prachi




On Tue, Sep 18, 2018 at 3:26 AM, Stepan Pilshchikov <
pilshchikov@gmail.com> wrote:

> > You know, I'm confused with all this documentation stuff...
> > For nodejs client all docs were moved from the repo to readme.io but
> the
> > readme.md keeps the installation instructions (duplicated with
> > readme.io). Probably, that's ok.
> > Will add similar short readme.md to the PHP PR.
>
> Its good
>
> What i think (and how it partially now):
> All user documentation should be on readme.io (how to install, use it,
> configurate, description for examples)
> All developers documentation (how to release, how to start develop) and(!)
> basic description should be in repository
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: Data streaming using Apache Ignite and Flink

[Prachi Garg]

Here's the link to the blogs page -  https://ignite.apache.org/blogs.html

On Wed, Sep 12, 2018 at 12:12 PM, Denis Magda  wrote:

> Prachi,
>
> Did you forget to add Saikat's blog to the list?
>
> --
> Denis
>
> On Wed, Sep 12, 2018 at 1:44 PM Dmitriy Pavlov 
> wrote:
>
>> Hi Denis,
>>
>> I didn't find the blog post there.
>>
>> Could you please add it or advice me how can I do it?
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> вт, 28 авг. 2018 г. в 4:19, Saikat Maitra :
>>
>> > Thank you so much Denis.
>> >
>> > Regards,
>> > Saikat
>> >
>> > On Mon, Aug 27, 2018 at 5:00 PM, Denis Magda  wrote:
>> >
>> > > Hello Saikat,
>> > >
>> > > Thanks for the article and contribution. We'll get it added to:
>> > > https://ignite.apache.org/blogs.html
>> > >
>> > > --
>> > > Denis
>> > >
>> > > On Sun, Aug 26, 2018 at 2:59 PM Saikat Maitra <
>> saikat.mai...@gmail.com>
>> > > wrote:
>> > >
>> > > > Hello,
>> > > >
>> > > > I recently published blog on how we can stream data using Apache
>> Ignite
>> > > and
>> > > > Flink. This uses IgniteSink with recent changes merged (release due
>> in
>> > > > 2.7.0) which will allow us to run IgniteSink using Apache Flink in
>> > > cluster
>> > > > mode.
>> > > >
>> > > >
>> > > >
>> > > > https://samaitra.blogspot.com/2018/08/data-streaming-using-
>> > > apache-flink-and.html
>> > > >
>> > > > Please review and let me know if you have feedback.
>> > > >
>> > > > Regards,
>> > > > Saikat
>> > > >
>> > >
>> >
>>
>

[jira] [Created] (IGNITE-9525) Ignite + Informatica Integration

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-9525:
---

 Summary: Ignite + Informatica Integration
 Key: IGNITE-9525
 URL: https://issues.apache.org/jira/browse/IGNITE-9525
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Prachi Garg
Assignee: Prachi Garg
 Fix For: 2.7


Mentioned in https://cwiki.apache.org/confluence/display/IGNITE/Required+Docs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9524) Ignite Spring Session Integration

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-9524:
---

 Summary: Ignite Spring Session Integration
 Key: IGNITE-9524
 URL: https://issues.apache.org/jira/browse/IGNITE-9524
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Prachi Garg
Assignee: Prachi Garg
 Fix For: 2.7


Mentioned in https://cwiki.apache.org/confluence/display/IGNITE/Required+Docs

 

[https://github.com/antkr/spring-session-ignite] and 
[https://github.com/antkr/spring-session-ignite-rest] - to be merged to Ignite

 

[https://apacheignite-mix.readme.io/docs] under "Spring" section with a 
reference from "web session clustering" section. Ignite web site needs to be 
updated as well - 
[https://ignite.apache.org/use-cases/caching/web-session-clustering.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9523) Document PHP thin client

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-9523:
---

 Summary: Document PHP thin client
 Key: IGNITE-9523
 URL: https://issues.apache.org/jira/browse/IGNITE-9523
 Project: Ignite
  Issue Type: Task
Reporter: Prachi Garg
Assignee: Prachi Garg
 Fix For: 2.7


Jira with the scope of work - [1].

Implementation, examples, tests:
  PR - [2],
  repository - [3].

API spec - [4].

Readme (how to for the client, instructions for the examples and tests, etc.) - 
[5].


[1] https://issues.apache.org/jira/browse/IGNITE-7783
[2] [https://github.com/apache/ignite/pull/4649]
[3] [https://github.com/nobitlost/ignite/tree/ignite-7783/modules/platforms/php]
[4] 
[https://rawgit.com/nobitlost/ignite/ignite-7783-docs/modules/platforms/php/api_docs/html/index.html]
[5] 
[https://github.com/nobitlost/ignite/blob/ignite-7783-docs/modules/platforms/php/README.md]
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9522) Document Python thin client

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-9522:
---

 Summary: Document Python thin client
 Key: IGNITE-9522
 URL: https://issues.apache.org/jira/browse/IGNITE-9522
 Project: Ignite
  Issue Type: Task
Reporter: Prachi Garg
Assignee: Prachi Garg
 Fix For: 2.7


Bring documentation from here - 
[https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/readme.html]
 into readme.io



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Thin Client lib: Python

[Prachi Garg]

Thanks Dmitry!

On Wed, Sep 5, 2018 at 11:59 PM, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:

> Hello, Prachi!
>
> The section is a hand-written .rst-file, which contains links to some
> content, generated from code with `sphinx-apidoc`.
>
> All autogenerated content resides in `source` folder. For example, this is
> an autogenerated page:
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/
> en/latest/source/pyignite.client.html
>
> And this is written by hand:
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/
> en/latest/datatypes/parsers.html
>
>
> On 9/6/18 9:39 AM, Prachi Garg wrote:
>
>> Hi Dmitry M,
>>
>> Is the API Specification [1] section of the documentation auto-generated
>> from the code?
>>
>> [1]
>> https://apache-ignite-binary-protocol-client.readthedocs.io/
>> en/latest/modules.html
>>
>>

Re: Thin Client lib: Python

[Prachi Garg]

Hi Dmitry M,

Is the API Specification [1] section of the documentation auto-generated
from the code?

[1]
https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/modules.html

On Mon, Jul 30, 2018 at 5:05 PM, Dmitriy Setrakyan 
wrote:

> Now we are talking. A much better and more user-friendly API.
>
> D.
>
> On Fri, Jul 27, 2018 at 7:19 AM, Dmitry Melnichuk <
> dmitry.melnic...@nobitlost.com> wrote:
>
> > Dmitriy, Igor, Ilya, Sergey!
> >
> > Thank you for sharing your ideas, concerns and criticism with me. I do
> > appreciate it.
> >
> > I already made some changes in my API, influenced by your feedback. I
> also
> > plan to add a certain set of features, that will make my UX closer to
> what
> > you can see from other Ignite clients.
> >
> > I stopped using `hashcode` in my examples. Integer cache IDs and cache
> > names now can be used interchangeably, with primary focus on cache names.
> >
> > I will add a Cache class as a primary interface for cache operations, so
> > that earlier examples:
> >
> > ```
> > conn = Connection()
> > conn.connect('127.0.0.1', 10800)
> >
> > cache_create(conn, 'my cache')
> >
> > cache_put(conn, 'my cache', 'my key', 42)
> > result = my_cache.get('my key')
> >
> > cache_destroy(conn, 'my cache')
> > conn.close()
> > ```
> >
> > could be reiterated as:
> >
> > ```
> > conn = Connection()
> > conn.connect('127.0.0.1', 10800)
> >
> > my_cache = conn.create_cache('my cache')
> >
> > my_cache.put('my key', 42)
> > result = my_cache.get('my key')
> >
> > my_cache.destroy('my cache')
> > conn.close()
> > ```
> >
> > I will also make `Connection.connect()` accept any iterable (including
> > simple list) as a connection parameter. I will provide user with some
> basic
> > connection generators instead of what is done in my current connection
> > failover example.
> >
> >
> > On 07/27/2018 07:41 AM, Dmitriy Setrakyan wrote:
> >
> >> Dmitriy,
> >>
> >> I would stop using the word "hashcode" in this context. Hash code has a
> >> special meaning in Ignite and is used to determine key-to-node
> affinity. I
> >> agree that passing "cache_name" is the best option. I have no idea when
> >> "cache_name" is not going to be known and do not think we need to
> support
> >> this case at all. My suggestion is to drop the cache_id use case
> >> altogether.
> >>
> >> Also I am really surprised that we do not have a cache abstraction in
> >> python and need to pass cache name and connection into every method. To
> be
> >> honest, this smells really bad that such a popular modern language like
> >> Python forces us to have such a clumsy API. Can you please take a look
> at
> >> the Redis python clients and see if there is a better way to support
> this?
> >>
> >> https://redis.io/clients#python
> >>
> >> D.
> >>
> >
>

Re: Thin Client lib: Python

[Prachi Garg]

Thanks Dmitry. I'll look at the docs.

On Wed, Jul 25, 2018 at 8:11 PM, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:

> Hi Prachi!
>
> At the moment I already have my documents (temporarily) published at RTD.
> This is how they look like at a whole:
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/
>
> I already have a separate section on examples:
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/
> en/latest/examples.html
>
> My build process is also documented here
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/
> en/latest/readme.html#documentation
>
> and there
>
> https://github.com/nobitlost/ignite/blob/ignite-7782/modules
> /platforms/python/README.md
>
> This instructions works for me, and I have at least one report of
> successful documentation build from elsewhere. And RTD is using basically
> the same way to put my docs online.
>
> My way of document building is pretty common for Python package
> developers, but if it needs some modifications to fit into Ignite process,
> please let me know.
>
> All the document sources (both autodoc'ed and hand-crafted) is available at
>
> https://github.com/nobitlost/ignite/tree/ignite-7782/modules
> /platforms/python/docs
>
> I will be glad to answer any questions.
>
>
> On 07/26/2018 06:25 AM, Prachi Garg wrote:
>
>> Hi Dmitry M,
>>
>> I am resposible for managing the Ignite documentation. At some point we
>> will merge the python documentation on github into the main Ignite
>> documentation. Currently, I am trying to restructure our thin client
>> documentation in a way that it (thin client documentation) is consistent
>> for all supported languages - Java, Node.js, Python etc.
>>
>> I looked at the python document on github. Under the :mod:`~pyignite.api`
>> section,  I see all the components - cache config, key value, sql, binary
>> types - but there are no code snippets. Is it possible for you describe
>> these components with code examples?
>>
>> See for example -
>> https://apacheignite.readme.io/docs/java-thin-client-api#sec
>> tion-sql-queries
>> where the SQL Queries section explains, with example, how the thin client
>> SQL API can be used.
>>
>> Similarly, please see -
>> https://apacheignite.readme.io/docs/java-thin-client-security
>> https://apacheignite.readme.io/docs/java-thin-client-high-availability
>> https://apacheignite.readme.io/docs/java-thin-client-api
>>
>> Thanks,
>> -Prachi
>>
>

Re: Thin Client lib: Python

[Prachi Garg]

Hi Dmitry M,

I am resposible for managing the Ignite documentation. At some point we
will merge the python documentation on github into the main Ignite
documentation. Currently, I am trying to restructure our thin client
documentation in a way that it (thin client documentation) is consistent
for all supported languages - Java, Node.js, Python etc.

I looked at the python document on github. Under the :mod:`~pyignite.api`
section,  I see all the components - cache config, key value, sql, binary
types - but there are no code snippets. Is it possible for you describe
these components with code examples?

See for example -
https://apacheignite.readme.io/docs/java-thin-client-api#section-sql-queries
where the SQL Queries section explains, with example, how the thin client
SQL API can be used.

Similarly, please see -
https://apacheignite.readme.io/docs/java-thin-client-security
https://apacheignite.readme.io/docs/java-thin-client-high-availability
https://apacheignite.readme.io/docs/java-thin-client-api

Thanks,
-Prachi


On Wed, Jul 25, 2018 at 12:46 PM, Dmitriy Setrakyan 
wrote:

> I am still confused. Let's work through an example. Suppose I have a cache
> named "my_cache" and I want to put an entry with key "a" and value "1".
>
> In Java, this code will look like this:
>
>
> > *IgniteCache<...> myCache = ignite.cache("my-cache");myCache.put("a",
> 1);*
>
>
> How will the same code look in Python?
>
> D.
>
> On Wed, Jul 25, 2018 at 5:08 PM, Dmitry Melnichuk <
> dmitry.melnic...@nobitlost.com> wrote:
>
> > Igor,
> >
> > That is a very good point. It just did not cross my mind during the
> > implementation of this function, that the cache identifier can be
> abstract.
> > I will fix that.
> >
> >
> > On 07/26/2018 01:46 AM, Igor Sapego wrote:
> >
> >> Well, at least name should be changed, IMO, as the API function name
> >> should say what we do, and not how we do it. For example, cache_id()
> >> looks better to me than hashcode().
> >>
> >> Best Regards,
> >> Igor
> >>
> >
>

Re: Documenting Ignite

[Prachi Garg]

I totally agree with Denis's point -

"Another benefit of having "Docs Required" flag enabled by default, is that
Artem and Prachi can see all such tickets months and weeks before a
release, figure out details from source code contributors and complete the
docs in advance."

On Wed, Jul 18, 2018 at 2:49 PM, Dmitry Pavlov 
wrote:

> Yes, I agree. My concern is related only to process implementation aspect,
> I wonder if it is technically possible.
>
> Generally I like idea of automatic control.
>
> ср, 18 июл. 2018 г. в 23:21, Denis Magda :
>
> > Hi folks,
> >
> > Artem's proposal might simplify and make our doc tickets tracking less
> > error-prone. The current approach implies that a contributor keeps in
> mind
> > what needs to go to the docs. If he/she has a good memory, a doc JIRA
> > counterpart will be created once the contribution is accepted. But the
> > practice shows that the memory lets us down :)
> >
> > Another benefit of having "Docs Required" flag enabled by default, is
> that
> > Artem and Prachi can see all such tickets months and weeks before a
> > release, figure out details from source code contributors and complete
> the
> > docs in advance.
> >
> > --
> > Denis
> >
> > On Wed, Jul 18, 2018 at 8:39 AM Artem Budnikov <
> > a.budnikov.ign...@gmail.com> wrote:
> >
> >> Dmitry,
> >>
> >> The goal I had in mind by proposing that suggestion was to rectify the
> >> fact that JIRA issues for documentation are created on an ad-hoc basis,
> >> and often issues are created when the lack of documentation becomes an
> >> issue for somebody. So we need to be more proactive.
> >>
> >> I think manual tracking of issues is possible but as efficient as the
> >> current situation with the docs. Manual tracking will have to be shared
> >> between multiple contributors and performed outside of JIRA, which has
> >> its own limitation. If you have any suggestions for improvement without
> >> creating fields in JIRA, please share your thoughts.
> >>
> >> If you are concerned that it's not possible to add a field, then we
> >> should contact Apache Infra and find out.
> >>
> >>
> >> Best regards,
> >>
> >> Artem Budnikov
> >>
> >>
> >> On 18.07.2018 16:14, Dmitry Pavlov wrote:
> >> > Hi Artem,
> >> >
> >> > I sometimes receive feedback that Ignite docs has potential for
> >> > improvement, while I found our docs quite intuitive and simple to
> >> > understand. So if experienced tech writer will join community it could
> >> > benefit all of us, and users, of course. So you're very welcome to the
> >> > community!
> >> >
> >> > About idea of fields introduction I guess we will need assistance of
> >> Apache
> >> > Infra team, because Ignite shares JIRA with all other Apache project.
> >> And
> >> > I'm not sure that technical implementation of proposed process is even
> >> > possible without plugins. Could we consider some manual processing of
> >> > completed issues in relation to doc requrement?
> >> >
> >> > Sincerely,
> >> > Dmitriy Pavlov
> >> >
> >> > ср, 18 июл. 2018 г. в 15:06, Artem Budnikov <
> >> a.budnikov.ign...@gmail.com>:
> >> >
> >> >> Hi Igniters,
> >> >>
> >> >> Being a technical writer, I'm going to contribute to Ignite's
> >> >> documentation, and I believe documentation is an important part of
> >> every
> >> >> product, especially such a complex product as Apache Ignite.
> >> >>
> >> >> I'd like to put forward a suggestion on how to increase our chances
> of
> >> >> making Ignite documentation more comprehensive. The basic idea is to
> >> >> have a Jira issue with the Component field set to "Documentation" for
> >> >> every feature that needs to be documented. This will ensure that
> there
> >> >> are documentation issues that cover the entire product functionality.
> >> >> Then someone can take on an issue and contribute an article on the
> >> subject.
> >> >>
> >> >> This is how I envision it to work technically. A new field (checkbox)
> >> is
> >> >> added to the Apache Ignite Jira project. The checkbox indicates that
> >> the
> >> >> feature requested in this issue needs to be documented. The checkbox
> is
> >> >> selected by default. If the feature does not require documentation,
> >> then
> >> >> the author unchecks the checkbox. If it does require documentation,
> the
> >> >> author creates a related Jira issue selecting "Documentation" in the
> >> >> Component field, providing details on what exactly should be
> >> documented.
> >> >>
> >> >> The field is called "Requires documentation" or similarly. It could
> be
> >> >> also useful to create a new issue type for documentation issues
> >> >> exclusively.
> >> >>
> >> >> Once this is done, we'll be able to filter out
> >> >>
> >> >>   1. issues that do not require documentation,
> >> >>   2. issues that have related documentation tickets, and
> >> >>   3. issues that require documentation but have no related issues
> >> (which
> >> >>  means that the author forgot to create a documentation issue for
> >> it).
> >> >>
> >> >>
> 

Re: About readme.io's latest docs

[Prachi Garg]

I already sent him the export, but the attachments were huge. I think
that's why the email reply was not received by the dev list.

-P

On Mon, Jul 9, 2018 at 2:33 PM, Dmitry Pavlov  wrote:

> Igniters, was this question solved? Is it possible to do such export?
>
> пт, 1 июн. 2018 г. в 19:40, 李玉珏@163 <18624049...@163.com>:
>
>> Prachi,
>>
>>
>> Can you help to export all the latest version of all documents to me?
>> I am ready to make a synchronization of the chinese version of the
>> document.
>>
>> thanks!
>>
>>
>> 在 2017/11/24 下午1:33, Prachi Garg 写道:
>> > Attached.
>> >
>> > On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163 <18624049...@163.com
>> > <mailto:18624049...@163.com>> wrote:
>> >
>> > Prachi,
>> >
>> >
>> > Can you help me to export all the latest version of all documents
>> > to me?
>> > I am ready to make a synchronization of the chinese version of the
>> > document.
>> >
>> > thanks!
>> >
>> > 在 2017/8/17 上午2:05, Prachi Garg 写道:
>> >> Please see attached.
>> >>
>> >> -P
>> >>
>> >> On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda > >> <mailto:dma...@gridgain.com>> wrote:
>> >>
>> >> Hi!
>> >>
>> >> Prachi is on vacation and will send you the latest version as
>> >> soon as she is back to work.
>> >>
>> >> —
>> >> Denis
>> >>
>> >>> On Aug 7, 2017, at 5:33 AM, 李玉珏@163 <18624049...@163.com
>> >>> <mailto:18624049...@163.com>> wrote:
>> >>>
>> >>>
>> >>> Prachi,
>> >>>
>> >>>
>> >>> Can you help me to export all the latest version of all
>> >>> documents to me?
>> >>> I am ready to make a synchronization of the chinese version
>> >>> of the document.
>> >>>
>> >>> thanks!
>> >>>
>> >>>
>> >>> 在 2017/5/13 上午12:48, Prachi Garg 写道:
>> >>>> See attached for cpp, .net and integrations documentation.
>> >>>>
>> >>>> -P
>> >>>>
>> >>>> On Fri, May 12, 2017 at 9:47 AM, Prachi Garg
>> >>>> mailto:pg...@gridgain.com>> wrote:
>> >>>>
>> >>>> See attached for java, file-system, and tools
>> >>>> documentation.
>> >>>>
>> >>>> -P
>> >>>>
>> >>>> On Fri, May 12, 2017 at 5:39 AM, 李玉珏@163
>> >>>> <18624049...@163.com <mailto:18624049...@163.com>>
>> wrote:
>> >>>>
>> >>>> Prachi,
>> >>>>
>> >>>>
>> >>>>     Can you help me to export all the latest version of
>> >>>> all documents to me?
>> >>>> I am ready to make a synchronization of the chinese
>> >>>> version of the document.
>> >>>>
>> >>>> thanks!
>> >>>>
>> >>>>
>> >>>> 在 2017/3/18 04:54, Prachi Garg 写道:
>> >>>>> Hi,
>> >>>>>
>> >>>>> Please see attached.
>> >>>>>
>> >>>>> -P
>> >>>>>
>> >>>>> On Fri, Mar 17, 2017 at 4:56 AM, 李玉珏@163
>> >>>>> <18624049...@163.com <mailto:18624049...@163.com>>
>> >>>>> wrote:
>> >>>>>
>> >>>>> Prachi,
>> >>>>>
>> >>>>>
>> >>>>> Can you help me to export all the latest
>> >>>>> version of all documents to me?
>> >>>>> I am ready to make a synchronization of the
>> >>>>> chinese version of the document.
>> >>>>>
>> >

Re: Erroneous Baseline Topology documentation

[Prachi Garg]

Ivan,

I have fixed the documentation for baseline topology. Please review -
https://apacheignite.readme.io/v2.5/docs/baseline-topology#section-cluster-activation

-P

On Thu, Jul 5, 2018 at 11:55 AM, Prachi Garg  wrote:

> Thanks Ivan. I will fix the doc accordingly.
>
> On Thu, Jul 5, 2018 at 5:31 AM, Ivan Rakov  wrote:
>
>> I guess just activating the cluster would add all the existing nodes to
>> the baseline topology?
>>
>> Exactly. Persistent cluster can't exist in active state without baseline
>> topology. First activation will establish BLT from current set of server
>> nodes.
>>
>> Best Regards,
>> Ivan Rakov
>>
>> On 04.07.2018 1:55, Prachi Garg wrote:
>>
>> Hi Ivan,
>>
>> I have fixed and rephrased the section - https://apacheignite.readme.
>> io/v2.5/docs/baseline-topology#section-cluster-activation
>>
>> However, I have a question regarding setting the baseline topology when
>> activating the cluster for the first time. In the web console, when we
>> activate the cluster, using the toggle switch, all server nodes in the
>> cluster are automatically added to the baseline topology. Does this mean
>> that when we activate the cluster for the first time, via code, we do not
>> need the following piece code?
>>
>> // Get all server nodes that are already up and running.
>> Collection nodes = ignite.cluster().forServers().nodes();
>>
>> // Set the baseline topology that is represented by these nodes.
>> ignite.cluster().setBaselineTopology(nodes);
>>
>> I guess just activating the cluster would add all the existing nodes to
>> the baseline topology?
>>
>>
>>
>> On Tue, Jul 3, 2018 at 12:48 PM, Ivan Rakov 
>> wrote:
>>
>>> I've tried to execute exactly the same code, it resulted with
>>>
>>> class org.apache.ignite.IgniteException: Changing BaselineTopology on
>>>> inactive cluster is not allowed.
>>>>
>>> Basically, the code snippet is in "Setting the Topology From Code"
>>> section, so we can make it correct by just removing "activation" and "first
>>> baseline topology" parts.
>>>
>>> Best Regards,
>>> Ivan Rakov
>>>
>>>
>>>
>>> On 03.07.2018 22:30, Denis Magda wrote:
>>>
>>>> Prachi,
>>>>
>>>> I do remember that that code, Ivan is referring to, worked fine for you.
>>>> Please double check. Probably you need to add
>>>> "ignite.cluster.activate()"
>>>> to the code snippet.
>>>>
>>>> --
>>>> Denis
>>>>
>>>> On Tue, Jul 3, 2018 at 12:19 PM Ivan Rakov 
>>>> wrote:
>>>>
>>>> Igniters,
>>>>>
>>>>> Seems like we have an inconsistency in our Baseline Topology
>>>>> documentation:
>>>>>
>>>>> https://apacheignite.readme.io/docs/baseline-topology#sectio
>>>>> n-setting-the-topology-from-code
>>>>>
>>>>> Java developers can use the IgniteCluster interface to initialize the
>>>>>> very first baseline topology or to adjust an existing one. The sample
>>>>>> below shows how to add all the existing server nodes to the baseline
>>>>>> topology:​
>>>>>> // Connecting to the cluster.
>>>>>> Ignite ignite = Ignition.start();
>>>>>>
>>>>>> // Setting the baseline topology to a specific Ignite cluster topology
>>>>>> version.
>>>>>> ignite.cluster().setBaselineTopology(2);
>>>>>>
>>>>> This is not true; baseline topology can't be changed on inactive
>>>>> cluster. The only viable way to initialize the very first baseline
>>>>> topology is manual cluster activation. This is correctly explained in
>>>>> this section:
>>>>>
>>>>> https://apacheignite.readme.io/docs/baseline-topology#sectio
>>>>> n-first-cluster-startup
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Ivan Rakov
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>

Re: Erroneous Baseline Topology documentation

[Prachi Garg]

Hi Ivan,

I have fixed and rephrased the section -
https://apacheignite.readme.io/v2.5/docs/baseline-topology#section-cluster-activation

However, I have a question regarding setting the baseline topology when
activating the cluster for the first time. In the web console, when we
activate the cluster, using the toggle switch, all server nodes in the
cluster are automatically added to the baseline topology. Does this mean
that when we activate the cluster for the first time, via code, we do not
need the following piece code?

// Get all server nodes that are already up and running.
Collection nodes = ignite.cluster().forServers().nodes();

// Set the baseline topology that is represented by these nodes.
ignite.cluster().setBaselineTopology(nodes);

I guess just activating the cluster would add all the existing nodes to the
baseline topology?



On Tue, Jul 3, 2018 at 12:48 PM, Ivan Rakov  wrote:

> I've tried to execute exactly the same code, it resulted with
>
> class org.apache.ignite.IgniteException: Changing BaselineTopology on
>> inactive cluster is not allowed.
>>
> Basically, the code snippet is in "Setting the Topology From Code"
> section, so we can make it correct by just removing "activation" and "first
> baseline topology" parts.
>
> Best Regards,
> Ivan Rakov
>
>
>
> On 03.07.2018 22:30, Denis Magda wrote:
>
>> Prachi,
>>
>> I do remember that that code, Ivan is referring to, worked fine for you.
>> Please double check. Probably you need to add "ignite.cluster.activate()"
>> to the code snippet.
>>
>> --
>> Denis
>>
>> On Tue, Jul 3, 2018 at 12:19 PM Ivan Rakov  wrote:
>>
>> Igniters,
>>>
>>> Seems like we have an inconsistency in our Baseline Topology
>>> documentation:
>>>
>>> https://apacheignite.readme.io/docs/baseline-topology#sectio
>>> n-setting-the-topology-from-code
>>>
>>> Java developers can use the IgniteCluster interface to initialize the
 very first baseline topology or to adjust an existing one. The sample
 below shows how to add all the existing server nodes to the baseline
 topology:​
 // Connecting to the cluster.
 Ignite ignite = Ignition.start();

 // Setting the baseline topology to a specific Ignite cluster topology
 version.
 ignite.cluster().setBaselineTopology(2);

>>> This is not true; baseline topology can't be changed on inactive
>>> cluster. The only viable way to initialize the very first baseline
>>> topology is manual cluster activation. This is correctly explained in
>>> this section:
>>>
>>> https://apacheignite.readme.io/docs/baseline-topology#sectio
>>> n-first-cluster-startup
>>>
>>> --
>>> Best Regards,
>>> Ivan Rakov
>>>
>>>
>>>
>

How to create a cache with 2 backups using REST

[Prachi Garg]

Hi Alexey,

I used the following command to create a cache with 2 backups -
http://localhost:8080/ignite?cmd=getorcreate=myNewPartionedCache=2

This is the response -
{“successStatus”:0,“error”:null,“response”:null,“sessionToken”:null}

Here, it does not give me much info in the response. Looking at the status,
which is 0, I can just assume that everything went ok.(I guess..)

Then I try to get the cache metadata, using this command -
http://localhost:8080/ignite?cmd=metadata=myNewPartionedCache

I get this error - {“successStatus”:1,“error”:“Failed to handle request:
[req=CACHE_METADATA, err=Failed to request meta data. myNewPartionedCache
is not found]“,”response”:null,“sessionToken”:null}

What am I missing here?

-P

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Prachi Garg]

Peter,

I updated the RPM and DEB description on the downloads page[1] (following
the instructions on the documentation [2]). Please check that the
repositories and installation instructions are up-to-date.

[1] https://ignite.apache.org/download.cgi#rpm-package
[2] https://apacheignite.readme.io/docs/getting-started#
section-rpm-deb-packages-installation


On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan 
wrote:

> I just tried the Debian install. This is what I got after executing "sudo
> apt get" command:
>
>
> >
> > *E: The repository 'https://apache.org/dist/ignite/deb
> > <https://apache.org/dist/ignite/deb> apache-ignite Release' does not
> have a
> > Release file.N: Updating from such a repository can't be done securely,
> and
> > is therefore disabled by default.N: See apt-secure(8) manpage for
> > repository creation and user configuration details.*
>
>
> D.
>
> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  wrote:
>
> > Andrey,
> >
> > Please help to generate 2.5 release HTML file and add it to Ignite
> website
> > SVN. Sergey K and Ilya S. should be able to assist with this.
> >
> > Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> > can't announce the release and close it without having the docs done.
> >
> > --
> > Denis
> >
> >
> > On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  wrote:
> >
> >> Folks,
> >>
> >> I have released 2.5 documentation on readme.io. Also, the downloads
> page
> >> on
> >> the website is updated with 2.5 release. Mauricio will work on updating
> >> the
> >> latest doc reference.
> >>
> >>
> >> Andrey,
> >>
> >> The following still needs attention:
> >>
> >>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/
> >>2. Zookeper documentation -
> >>https://issues.apache.org/jira/browse/IGNITE-7900
> >>3. Consistency check utilities docs -
> >>https://issues.apache.org/jira/browse/IGNITE-8524
> >>
> >>
> >> Thanks,
> >> -Prachi
> >>
> >> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  wrote:
> >>
> >> > Pavel,
> >> >
> >> > Thanks a lot!
> >> >
> >> >
> >> >
> >> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
> >> >
> >> > > NuGet (.NET) packages pushed:
> >> > > https://www.nuget.org/packages?q=Apache.Ignite
> >> > >
> >> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura 
> >> wrote:
> >> > >
> >> > >> Dmitry,
> >> > >>
> >> > >> First we should check docker images. Also we are waiting for
> >> > >> publishing of artifacts to Maven Central.
> >> > >>
> >> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> >> > >>  wrote:
> >> > >> >
> >> > >> >
> >> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura 
> >> > wrote:
> >> > >> >>
> >> > >> >> RPM and DEB packages are published to bintray [1] [2]
> >> > >> >>
> >> > >> >> [1] https://bintray.com/apache/ignite-rpm
> >> > >> >> [2] https://bintray.com/apache/ignite-deb
> >> > >> >
> >> > >> >
> >> > >> > Thanks, Andrey! Can we update the download page on the website?
> >> > >> >
> >> > >> > D.
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
>

[jira] [Created] (IGNITE-8549) Include SSL related parameters for JDBC/ODBC

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-8549:
---

 Summary: Include SSL related parameters for JDBC/ODBC
 Key: IGNITE-8549
 URL: https://issues.apache.org/jira/browse/IGNITE-8549
 Project: Ignite
  Issue Type: Task
Reporter: Prachi Garg
Assignee: Prachi Garg
 Fix For: 2.5


DRIVER=\{Apache 
Ignite};ADDRESS=13.56.76.37:9954;USER=ignite;PASSWORD=1mSBcc8loX;*SSL_MODE=require;SSL_KEY_FILE=client.pem;SSL_CERT_FILE=client.pem;SSL_CA_FILE=client.pem*
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Move documentation from readme.io to GitHub pages

[Prachi Garg]

I did a very shallow research on Jekyll. Work flow seemed similar to
Docusaurus but more flexible in terms of directory structure- how docs can
be placed in the repo (Docusaurus requires docs to be stored in a
particular directory structure), as well as sidebar menu ( Docusaurus does
not allow child pages). Additionally, if so many open source projects are
using Jekyll, then I think it's definitely worth a try.

-Prachi

On Tue, Apr 10, 2018 at 4:52 PM, Denis Magda <dma...@gridgain.com> wrote:

> Look into both Docusaraus and Jekyll from the usage perspective. Here is
> my summary:
>
> *Documentation Sources *
>
> Will be stored on GitHub. My preference is to store them in "ignite/docs"
> folder as many other ASF projects do (Spark [1], Flink [2] and Storm [3]).
> If we need to update the sources of an already released version, then we
> can create ignite-{version}-docs branch, edit it directly and generate HTML
> pages from it.
>
> *Versioning*
>
> Since the docs are stored in the main repo, a doc version will correspond
> to an Ignite version. If changes incorporated in the master version of the
> docs have to be merged to a previous version and redeployed on the site, we
> will use standard 'git' facilities to propagate the changes whenever is
> needed.
>
> *Documentation Deployment and Automation*
>
> Documentation engines usually go with a set of scripts that produce an
> HTML version of the docs out of the sources. In our scenario, we will use
> the scripts to convert the sources stored in GitHub to HTML pages stored in
> SVN repo of Ignite site. The docs' HTML pages will be hosted on
> ignite.apache.org.
>
> By default, the one has to run the scripts on a local machine to produce
> the HTML pages. However, nothing prevents us from tweaking the scripts and
> using them in a way that would do this on a fly - "a page has changed in
> sources"->"update site button is pressed"->"HTML is generated and
> automatically deployed to the site".
>
>
> Btw, *Prachi*, have you checked up Jekyll [4]? It's used by Spark, Flink,
> Storm, and even Github Pages. It's simpler than Docusarus and still gives a
> way to generate customized sites with navigation menus and table of
> contents: https://ci.apache.org/projects/flink/flink-docs-release-1.4/
>
>
> Does anyone else have any open questions we need to solve before starting
> a migration process?
>
>
>
> [1] https://github.com/apache/spark/tree/master/docs
> [2] https://github.com/apache/flink/tree/master/docs
> [3] https://github.com/apache/storm/tree/master/docs
> [4] https://github.com/jekyll/jekyll
>
> On Wed, Mar 21, 2018 at 6:15 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
> wrote:
>
>> On Wed, Mar 21, 2018 at 9:27 PM, Prachi Garg <pg...@gridgain.com> wrote:
>>
>> > We can store the project (Markdown & Docusaurus config files) in Git,
>> use
>> > Docusaurus to build html, and upload them to Ignite website.
>> >
>>
>> Sounds good!
>>
>
>

[jira] [Created] (IGNITE-8198) Document how to use username/password for REST and thin protocol connections

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-8198:
---

 Summary: Document how to use username/password for REST and thin 
protocol connections
 Key: IGNITE-8198
 URL: https://issues.apache.org/jira/browse/IGNITE-8198
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.5
Reporter: Prachi Garg
Assignee: Prachi Garg
 Fix For: 2.5


Update REST protocol - [https://apacheignite.readme.io/docs/rest-api]

and binary protocol documentation - 
https://apacheignite.readme.io/docs/binary-client-protocol#section-handshake



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Ignite Direct I/O plugin description added to wiki

[Prachi Garg]

Dmitriy,

I have documented the Direct I/O plugin. Please review [1] and provide
comments/feedback in the ticket [2].

[1]
https://apacheignite.readme.io/v2.4/docs/durable-memory-tuning#section-enabling-direct-i-o

[2] https://issues.apache.org/jira/browse/IGNITE-7466


-Prachi

On Wed, Mar 21, 2018 at 11:22 PM, Dmitry Pavlov 
wrote:

> Yes, will do.
>
> чт, 22 мар. 2018 г. в 1:05, Denis Magda :
>
> > Dmitriy,
> >
> > Thanks for updating the WAL section. Now it makes total sense to me.
> >
> > As for the page with JNA projects, let's get added there! Could you
> > contact the owners?
> >
> > --
> > Denis
> >
> >
> > On Wed, Mar 21, 2018 at 9:27 AM, Dmitry Pavlov 
> > wrote:
> >
> >> Denis,
> >>
> >> one more thing, can/should we mention Ignite Direct IO plugin in list of
> >> project using JNA here: https://github.com/java-native-access/jna
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> ср, 21 мар. 2018 г. в 1:59, Denis Magda :
> >>
> >>> *Dmitriy*, thanks. Astonishing job! We'll add a section to the durable
> >>> memory tuning page and refer to the wiki for more details:
> >>> https://issues.apache.org/jira/browse/IGNITE-7466
> >>>
> >>> Please clarify the following:
> >>>
> >>> > Direct I/O mode can't be enabled for Write Ahead Log files. However,
> >>> when
> >>> > working with plugin, WAL manager applies advising Linux systems do
> not
> >>> > store the data of the file in page cache as they are not required.
> >>>
> >>>
> >>> For me, it means that WAL always goes through the operating system I/O
> >>> calls. Nothing changes for the WAL. However, I'm not sure what you
> meant
> >>> to
> >>> explain by saying "when working with the plugin (Direct I/O) WAL
> manager
> >>> applies...". Could you rephrase it to bring more clarity?
> >>>
> >>> *Raymond,*
> >>>
> >>>
> >>> If Direct I/O is enabled by default it will bring down the performance
> of
> >>> read-intensive application because, as Dmitry says, the reads bypass
> page
> >>> cache. So, I would recommend using it for write-intensive workloads
> and,
> >>> probably, for mixed-workloads depending on the reads and writes rate.
> >>>
> >>> --
> >>> Denis
> >>>
> >>>
> >>> On Tue, Mar 20, 2018 at 2:29 PM, Raymond Wilson <
> >>> raymond_wil...@trimble.com>
> >>> wrote:
> >>>
> >>> > Looks good!
> >>> >
> >>> > Is there any reason why this should not be a default setting if it
> >>> > gracefully downgrades to non-Direct IO if not supported by the OS?
> >>> >
> >>> > Thanks,
> >>> > Raymond.
> >>> >
> >>> > -Original Message-
> >>> > From: Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
> >>> > Sent: Wednesday, March 21, 2018 10:23 AM
> >>> > To: dev 
> >>> > Subject: Re: Ignite Direct I/O plugin description added to wiki
> >>> >
> >>> > Thanks Dmitry, awesome work!
> >>> >
> >>> > On Wed, Mar 21, 2018 at 12:21 AM, Dmitry Pavlov <
> dpavlov@gmail.com
> >>> >
> >>> > wrote:
> >>> >
> >>> > > Hi Igniters,
> >>> > >
> >>> > > I've added description of new plugin for Direct I/O for native
> >>> > > persistence (
> >>> > > https://issues.apache.org/jira/browse/IGNITE-6341)  to wiki
> >>> > > https://cwiki.apache.org/confluence/display/IGNITE/
> >>> > > Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-
> >>> > > underthehood-DirectI/O
> >>> > >
> >>> > >
> >>> > > SIncerely,
> >>> > > Dmitriy Pavlov
> >>> > >
> >>> >
> >>>
> >>
> >
>

Re: readme.io weird interface element

[Prachi Garg]

Thanks Petr. I'll look into it.

On Wed, Mar 21, 2018 at 12:44 AM, Petr Ivanov <mr.wei...@gmail.com> wrote:

> Filed https://issues.apache.org/jira/browse/IGNITE-8003
>
>
>
> > On 20 Mar 2018, at 21:14, Prachi Garg <pg...@gridgain.com> wrote:
> >
> > Hi Petr, Denis,
> >
> > Sorry missed the message. Petr, please feel free to create a ticket.
> >
> > Thanks,
> > -Prachi
> >
> >
> > On Mon, Mar 19, 2018 at 8:24 PM, Petr Ivanov <mr.wei...@gmail.com>
> wrote:
> >
> >> Prachi, has you filed the ticket or should I create one?
> >>
> >>
> >>
> >>> On 15 Mar 2018, at 23:07, Denis Magda <dma...@apache.org> wrote:
> >>>
> >>> Please create a ticket and let's fix it in the nearest future.
> >>>
> >>> --
> >>> Denis
> >>>
> >>> On Thu, Mar 15, 2018 at 12:47 PM, Prachi Garg <pg...@gridgain.com>
> >> wrote:
> >>>
> >>>> That's the download button. Tables on feature pages are downloadable
> in
> >>>> pdf, csv format. There is a javascript code embedded with the table
> >>>> element. Not sure why it doesn't work on the download page; works fine
> >> on
> >>>> other pages.
> >>>>
> >>>> On Thu, Mar 15, 2018 at 12:16 PM, Denis Magda <dma...@apache.org>
> >> wrote:
> >>>>
> >>>>> Have no idea, just makes the table looks nicer :)
> >>>>>
> >>>>> Prachi, what is this for? It's not clear from the HTML sources.
> >>>>>
> >>>>> --
> >>>>> Denis
> >>>>>
> >>>>> On Thu, Mar 15, 2018 at 12:09 PM, Petr Ivanov <mr.wei...@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>>> Sorry for misleading. I meant https://ignite.apache.org/
> download.cgi
> >>>>>> indeed.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On 15 Mar 2018, at 22:05, Denis Magda <dma...@apache.org> wrote:
> >>>>>>>
> >>>>>>> Petr,
> >>>>>>>
> >>>>>>> What's that? It doesn't look like the readme.io doc that hosts all
> >>>>>> Ignite
> >>>>>>> docs:
> >>>>>>> https://apacheignite.readme.io/docs
> >>>>>>>
> >>>>>>> --
> >>>>>>> Denis
> >>>>>>>
> >>>>>>> On Thu, Mar 15, 2018 at 1:52 AM, vveider <mr.wei...@gmail.com>
> >> wrote:
> >>>>>>>
> >>>>>>>> Hi, all!
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Does anyone know what is this button with arrow and disk at the
> >> right
> >>>>>>>> corner
> >>>>>>>> of versions list header? [1]
> >>>>>>>> Seems that it does nothing.
> >>>>>>>>
> >>>>>>>> [1] https://ibb.co/eJf5uc
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
>
>

Re: Move documentation from readme.io to GitHub pages

[Prachi Garg]

We can store the project (Markdown & Docusaurus config files) in Git, use
Docusaurus to build html, and upload them to Ignite website.

On Tue, Mar 20, 2018 at 10:29 PM, Dmitriy Setrakyan 
wrote:

> Does docusaurus work with GitHub only, or with Git in general? In Apache
> GitHub is used as a mirror of an internal Git repo, which is the primary
> source of data.
>
> D.
>

Re: Move documentation from readme.io to GitHub pages

[Prachi Garg]

I looked into Docusaurus and GitBook. I liked Docusaurus better because it
allows publishing to github pages or other static files hosts, and various
other features. My findings are mentioned in the ticket -
https://issues.apache.org/jira/browse/IGNITE-7595 .

On Fri, Feb 2, 2018 at 2:42 PM, Denis Magda  wrote:

> Looks promising. Thanks for sharing. Updated the ticket.
>
> —
> Denis
>
> > On Feb 2, 2018, at 2:25 PM, Dmitriy Setrakyan 
> wrote:
> >
> > I think docusaurus.io could work for us. Denis, what do you think?
> >
> > On Fri, Feb 2, 2018 at 3:10 AM, endianignite 
> wrote:
> >
> >> I noticed that Facebook open-sourced a documentation platform last
> month,
> >> https://docusaurus.io/, which may be worth considering.
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >>
>
>

Re: readme.io weird interface element

[Prachi Garg]

Hi Petr, Denis,

Sorry missed the message. Petr, please feel free to create a ticket.

Thanks,
-Prachi


On Mon, Mar 19, 2018 at 8:24 PM, Petr Ivanov <mr.wei...@gmail.com> wrote:

> Prachi, has you filed the ticket or should I create one?
>
>
>
> > On 15 Mar 2018, at 23:07, Denis Magda <dma...@apache.org> wrote:
> >
> > Please create a ticket and let's fix it in the nearest future.
> >
> > --
> > Denis
> >
> > On Thu, Mar 15, 2018 at 12:47 PM, Prachi Garg <pg...@gridgain.com>
> wrote:
> >
> >> That's the download button. Tables on feature pages are downloadable in
> >> pdf, csv format. There is a javascript code embedded with the table
> >> element. Not sure why it doesn't work on the download page; works fine
> on
> >> other pages.
> >>
> >> On Thu, Mar 15, 2018 at 12:16 PM, Denis Magda <dma...@apache.org>
> wrote:
> >>
> >>> Have no idea, just makes the table looks nicer :)
> >>>
> >>> Prachi, what is this for? It's not clear from the HTML sources.
> >>>
> >>> --
> >>> Denis
> >>>
> >>> On Thu, Mar 15, 2018 at 12:09 PM, Petr Ivanov <mr.wei...@gmail.com>
> >> wrote:
> >>>
> >>>> Sorry for misleading. I meant https://ignite.apache.org/download.cgi
> >>>> indeed.
> >>>>
> >>>>
> >>>>
> >>>>> On 15 Mar 2018, at 22:05, Denis Magda <dma...@apache.org> wrote:
> >>>>>
> >>>>> Petr,
> >>>>>
> >>>>> What's that? It doesn't look like the readme.io doc that hosts all
> >>>> Ignite
> >>>>> docs:
> >>>>> https://apacheignite.readme.io/docs
> >>>>>
> >>>>> --
> >>>>> Denis
> >>>>>
> >>>>> On Thu, Mar 15, 2018 at 1:52 AM, vveider <mr.wei...@gmail.com>
> wrote:
> >>>>>
> >>>>>> Hi, all!
> >>>>>>
> >>>>>>
> >>>>>> Does anyone know what is this button with arrow and disk at the
> right
> >>>>>> corner
> >>>>>> of versions list header? [1]
> >>>>>> Seems that it does nothing.
> >>>>>>
> >>>>>> [1] https://ibb.co/eJf5uc
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >>>>>>
> >>>>
> >>>>
> >>>
> >>
>
>

Re: readme.io weird interface element

[Prachi Garg]

That's the download button. Tables on feature pages are downloadable in
pdf, csv format. There is a javascript code embedded with the table
element. Not sure why it doesn't work on the download page; works fine on
other pages.

On Thu, Mar 15, 2018 at 12:16 PM, Denis Magda  wrote:

> Have no idea, just makes the table looks nicer :)
>
> Prachi, what is this for? It's not clear from the HTML sources.
>
> --
> Denis
>
> On Thu, Mar 15, 2018 at 12:09 PM, Petr Ivanov  wrote:
>
>> Sorry for misleading. I meant https://ignite.apache.org/download.cgi
>> indeed.
>>
>>
>>
>> > On 15 Mar 2018, at 22:05, Denis Magda  wrote:
>> >
>> > Petr,
>> >
>> > What's that? It doesn't look like the readme.io doc that hosts all
>> Ignite
>> > docs:
>> > https://apacheignite.readme.io/docs
>> >
>> > --
>> > Denis
>> >
>> > On Thu, Mar 15, 2018 at 1:52 AM, vveider  wrote:
>> >
>> >> Hi, all!
>> >>
>> >>
>> >> Does anyone know what is this button with arrow and disk at the right
>> >> corner
>> >> of versions list header? [1]
>> >> Seems that it does nothing.
>> >>
>> >> [1] https://ibb.co/eJf5uc
>> >>
>> >>
>> >>
>> >> --
>> >> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>> >>
>>
>>
>

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

[Prachi Garg]

The latest 2.4 documentation is now available on readme.io  -
https://apacheignite.readme.io/docs/

-Prachi

On Mon, Mar 12, 2018 at 7:36 AM, Pavel Tupitsyn 
wrote:

> NuGet packages uploaded: https://www.nuget.org/packages?q=Apache.Ignite
>
> Thanks,
> Pavel
>
>
> On Mon, Mar 12, 2018 at 1:54 PM, Vladimir Ozerov 
> wrote:
>
> > Correct, it is a matter of time. Download links already work on my side
> > [1].
> >
> > [1] http://mirror.linux-ia64.org/apache/ignite/2.4.0/
> >
> > On Mon, Mar 12, 2018 at 1:29 PM, Petr Ivanov 
> wrote:
> >
> > > Link to 2.4.0 is pointing to RBC mirror, not Apache Dist itself.
> > >
> > > I do not know how often RBC updates its mirror, but I think we have to
> > > devise better solution for pointing to fresh release artifacts.
> > >
> > >
> > >
> > > > On 12 Mar 2018, at 13:24, Pavel Tupitsyn 
> wrote:
> > > >
> > > > Hi Vladimir,
> > > >
> > > > I see the link for 2.4.0 on https://ignite.apache.org/
> > > download.cgi#binaries,
> > > > but it does not work.
> > > >
> > > > On Mon, Mar 12, 2018 at 10:55 AM, Vladimir Ozerov <
> > voze...@gridgain.com>
> > > > wrote:
> > > >
> > > >> Correction: " Apache Ignite *2.4.0* release (RC1) has been
> accepted."
> > > >>
> > > >> On Mon, Mar 12, 2018 at 10:51 AM, Vladimir Ozerov <
> > voze...@gridgain.com
> > > >
> > > >> wrote:
> > > >>
> > > >>> Igniters,
> > > >>>
> > > >>> Apache Ignite 2.3.0 release (RC1) has been accepted.
> > > >>>
> > > >>> 5 "+1" binding votes received:
> > > >>> - Alexey Goncharuk
> > > >>> - Alexey Kuznetsov
> > > >>> - Anton Vinogradov
> > > >>> - Denis Magda
> > > >>> - Pavel Tupitsyn
> > > >>>
> > > >>> Vote thread:
> > > >>>
> > > >>> *http://apache-ignite-developers.2346864.n4.nabble.
> > > >> com/VOTE-Apache-Ignite-2-4-0-RC1-td27687.html
> > > >>>  > > >> com/VOTE-Apache-Ignite-2-4-0-RC1-td27687.html>*
> > > >>>
> > > >>> Ignite 2.4.0 will be released soon.
> > > >>>
> > > >>> Vladimir.
> > > >>>
> > > >>
> > >
> > >
> >
>

[jira] [Created] (IGNITE-7902) Enable either swap space or persistence but not both

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-7902:
---

 Summary: Enable either swap space or persistence but not both 
 Key: IGNITE-7902
 URL: https://issues.apache.org/jira/browse/IGNITE-7902
 Project: Ignite
  Issue Type: Task
Reporter: Prachi Garg
Assignee: Ivan Rakov
 Fix For: 2.5


Enabling both swap and persistence at the same time for a data region does not 
make sense. An exception should be thrown in this case.

See discussion - 
http://apache-ignite-developers.2346864.n4.nabble.com/Enabling-swap-space-and-Ignite-Persistence-td27595.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7886) Provide a list of node Ids on the Baseline page on Web Console

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-7886:
---

 Summary: Provide a list of node Ids on the Baseline page on Web 
Console
 Key: IGNITE-7886
 URL: https://issues.apache.org/jira/browse/IGNITE-7886
 Project: Ignite
  Issue Type: Bug
Reporter: Prachi Garg
Assignee: Alexey Kuznetsov
 Fix For: 2.4


It seems that the only way to get node IDs (needed for baseline topology) is 
from Web Console ->Monitoring ->Dashboard ->Node -> select node -> click Info 
-> General. However, Monitoring is not part of Ignite. Additionally, on the 
baseline page, on the web console, there is no list of nodes (or node Ids) to 
select from; it's blank. There should be a list of nodes that can be selected 
for baseline topology. Could this issue be related to - 
https://issues.apache.org/jira/browse/IGNITE-7885 ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7885) Error on Baseline page on Web Console

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-7885:
---

 Summary: Error on Baseline page on Web Console
 Key: IGNITE-7885
 URL: https://issues.apache.org/jira/browse/IGNITE-7885
 Project: Ignite
  Issue Type: Bug
Reporter: Prachi Garg
Assignee: Alexey Kuznetsov
 Fix For: 2.4


Every time I go to the baseline page on the web console, I get the following 
error -
{code:java}
Failed to handle request: [req=EXE, 
taskName=org.apache.ignite.internal.visor.compute.VisorGatewayTask, 
params=[null, org.apache.ignite.internal.visor.baseline.VisorBaselineTask, 
org.apache.ignite.internal.visor.baseline.VisorBaselineTaskArg, COLLECT, -1, 
java.util.List, java.lang.String, null], 
err=org.apache.ignite.internal.visor.baseline.VisorBaselineTaskArg]{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: REST: support getting objects from cache.

[Prachi Garg]

Thanks, Alexey! I'll update the docs.

-P

On Fri, Mar 2, 2018 at 1:42 AM, Alexey Kuznetsov 
wrote:

> I merged IGNITE-7803 into master.
> Created ticket for documentation: https://issues.
> apache.org/jira/browse/IGNITE-7867
>
> Prachi, could you update documentation for REST?
>
> On Thu, Mar 1, 2018 at 2:41 PM, Alexey Kuznetsov 
> wrote:
>
>> Vladimir,
>>
>> I finished with this feature: https://issues.apache
>> .org/jira/browse/IGNITE-7803
>>
>> Could you please review my changes in branch ignite-7803?
>>
>> DIFF: https://github.com/apache/ignite/commit/da03195ef5c39deabfc4
>> 961b2a0336fdbc98aa31
>>
>> --
>> Alexey Kuznetsov
>>
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Enabling swap space and Ignite Persistence

[Prachi Garg]

Engineers,

How does persistence and swap work when both are enabled? I was under the
impression that for a data region you can either have swap or persistence
configured at a time, but not both. Please clarify.

Thanks,
-Prachi

SQL Compliance documentation

[Prachi Garg]

Igniters,

Apache Ignite's compliance to SQL:1999 (Core) is now documented on readme.io[1]
as well as on Wikipedia[2]. SQL folks, check it out and let me know if
there needs to be any correction.

Thanks to Aleksandr Volkov for validating Ignite's compliance with SQL99
Core specification.

[1] https://apacheignite-sql.readme.io/docs/sql-conformance
[2] https://en.wikipedia.org/wiki/SQL_compliance


-Prachi

Documentation for Binary Client Protocol

[Prachi Garg]

Igniters,

The document for Binary Client Protocol (awaiting 2.4 release) is ready on
Apache Ignite readme.io. This document explains:

   - How to connect to Ignite cluster
   - Common message format (Request/Response header)
   - Supported Data types and their format
   - Request/Response format for each message type

Here are the links -

https://apacheignite.readme.io/docs/binary-client-protocol

https://apacheignite.readme.io/docs/binary-client-protocol-key-value-operations

https://apacheignite.readme.io/docs/binary-client-protocol-sql-operations

https://apacheignite.readme.io/docs/binary-client-protocol-binary-type-operations

https://apacheignite.readme.io/docs/binary-client-protocol-cache-configuration-operations


Currently these pages are hidden and are accessible only with the link.
They will be active after the release.

-Prachi

Binary protocol documentation

[Prachi Garg]

Hi Pavel,

I have a few more questions regarding the binary protocol.

1. OP_GET_BINARY_TYPE


   - Response returns array (not mentioned in the wiki doc), but
   OP_PUT_BINARY_TYPE does not require to pass an array. Wiki doc need to be
   fixed.
   - Response returns Schema Id as well (not mentioned in the left column
   of the spec for OP_GET_BINARY_TYPE; needs to be fixed in the wiki doc).


2. OP_QUERY_SCAN


   - Response returns only Cursor Id ( as mentioned in the wiki doc).
   However, OP_QUERY_SCAN_CURSOR_GET_PAGE returns complete query data. Why
   doesn't OP_QUERY_SCAN return query data? Why is the user supposed to call
   OP_QUERY_SCAN_CURSOR_GET_PAGE to get the data?

If you update the wiki doc, please update the document as well. The
document links are mentioned in this ticket - https://issues.apache.org/
jira/browse/IGNITE-6607

Thanks,
-Prachi

Re: Thin Client examples for documentation

[Prachi Garg]

Pavel,

I don't see any attachment. Can you please resend.

-P

On Thu, Jan 11, 2018 at 7:36 AM, Pavel Tupitsyn <ptupit...@gridgain.com>
wrote:

> Hi Prachi,
>
> I've fixed cache creation method for you, see attachment. I did not fix
> anything else.
> Sorry, but this kind of code with hardcoded message lengths, operation
> codes, etc is very hard to work with.
> Hardcoded values may be useful for trivial operations so that users get an
> idea of the protocol.
> But for complex stuff like SQL this gets out of hand quickly.
>
> My recommendations:
> - Create a common SendRequest method which will deal with message lengths,
> op codes and request ids automatically
> - Create writeString method to deal with UTF stuff in one place
> - When something does not work, use debugger on the server side
> (see ClientMessageParser class), it is easy to step through and see which
> value went wrong
>
> Thanks,
> Pavel
>
> On Wed, Jan 10, 2018 at 11:58 PM, Denis Magda <dma...@apache.org> wrote:
>
>> Pavel, as a side note,
>>
>> The methods/operations Prachi is struggling with look pretty standard to
>> me.
>>
>> Do you have tests for them in the code base? I mean *not* the tests you
>> shared before where we use existing internal binary marshaller APIs but
>> where we code every operation from scratch (what Prachi is doing for
>> documentation code snippets).
>>
>> Such tests would help to complete the doc quicker and would ensure that
>> the protocol works as expected on the user side where people are not going
>> to sit on the internal binary marshaller apis.
>>
>> —
>> Denis
>>
>> > On Jan 10, 2018, at 12:29 PM, Prachi Garg <pg...@gridgain.com> wrote:
>> >
>> > Pavel,
>> >
>> > I am having trouble creating examples for some of the thin protocol
>> > operations. I have uploaded my project on github -
>> >
>> > https://github.com/pgarg/ignite-examples/blob/master/src/
>> main/java/ignite/myexamples/thinclient/ThinClientExample2.java
>> >
>> > Please look into the following methods and provide a fix for them:
>> >
>> >   - doSQLQuery()
>> >   - getQueryCursorPage()
>> >   - putBinaryType()
>> >   - doQueryScan()
>> >   - createCacheWithConfiguration()
>> >
>> > Thanks,
>> > -Prachi
>>
>>
>

Thin Client examples for documentation

[Prachi Garg]

Pavel,

I am having trouble creating examples for some of the thin protocol
operations. I have uploaded my project on github -

https://github.com/pgarg/ignite-examples/blob/master/src/main/java/ignite/myexamples/thinclient/ThinClientExample2.java

Please look into the following methods and provide a fix for them:

   - doSQLQuery()
   - getQueryCursorPage()
   - putBinaryType()
   - doQueryScan()
   - createCacheWithConfiguration()

Thanks,
-Prachi

Thin Client documentation: OP_QUERY_SQL_CURSOR_GET_PAGE

[Prachi Garg]

Pavel,

I have 2 records in my cache, and when I run an example for
OP_QUERY_SQL=2002 with cursor page size 1, I get the following result
(expected)

len: 83
resReqId: 1
status code: 0
cursorId: 1
rowCount: 1
moreResults: true

Then, I run the OP_QUERY_SQL_CURSOR_GET_PAGE = 2003, using the following
code:

DataOutputStream out = new DataOutputStream(socket.getOutputStream());

// Message length
writeIntLittleEndian(18, out);

// Op code = QUERY_SQL_CURSOR_GET_PAGE
writeShortLittleEndian(2003, out);

// Request id (can be anything)
long reqId = 1;
writeLongLittleEndian(reqId, out);

// Cursor Id
writeLongLittleEndian(1, out);

// Send request
out.flush();

// Read result
DataInputStream in = new DataInputStream(socket.getInputStream());

// Response length
final int len = readIntLittleEndian(in);
System.out.println("len: " + len);

// Request id
long resReqId = readLongLittleEndian(in);
System.out.println("resReqId: " + resReqId);

// Success
int statusCode = readIntLittleEndian(in);
System.out.println("status code: " + statusCode);

int rowCount = readIntLittleEndian(in);
System.out.println("rowCount: " + rowCount);

// Read entries (as user objects)
for (int i = 0; i < rowCount; i++){
// ...
}

boolean moreResults = readBooleanLittleEndian(in);
System.out.println("moreResults: " + moreResults);

but the result is not what is expected:

len: 1
resReqId: 44096429228032
status code: 721512192
rowCount: 1672392448
moreResults: true

Also, there is no error on server side.

Anything wrong in the OP_QUERY_SQL_CURSOR_GET_PAGE request that I am
sending?

-Prachi

Example for OP_PUT_BINARY_TYPE

[Prachi Garg]

Pavel,

I am trying to come up with an example for OP_PUT_BINARY_TYPE = 3003.
However, few things are not clear to me from the wiki doc -

1. In BinaryField, What is Field id?
2. If there is no enum, what should I put for 'Enum values'?
3. What is Schema?

-P

Create cache using thin protocol

[Prachi Garg]

Pavel,

I tried to create a cache with configuration, using the thin protocol.

1. Do I need to provide every configuration as mentioned in the wiki, or I
can just provide a few and the rest can be default?

2. Using the below code:

DataOutputStream out = new DataOutputStream(socket.getOutputStream());

// Message length
writeIntLittleEndian(22, out);

// Op code = OP_CACHE_CREATE_WITH_CONFIGURATION
writeShortLittleEndian(1053, out);

// Request id (can be anything)
long reqId = 1;
writeLongLittleEndian(reqId, out);

// CacheAtomicityMode
writeIntLittleEndian(0, out);

// Backups
writeIntLittleEndian(2, out);

// CacheMode
writeIntLittleEndian(2, out);

// Read result
DataInputStream in = new DataInputStream(socket.getInputStream());

// Response length
final int len = readIntLittleEndian(in);
System.out.println("len: " + len);

// Request id
long resReqId = readLongLittleEndian(in);
System.out.println("resReqId: " + resReqId);

// Success
int statusCode = readIntLittleEndian(in);
System.out.println("status code: " + statusCode);


I get the following error:

[2017-12-20 
16:43:32,800][ERROR][client-connector-#45][ClientListenerNioListener]
Failed to parse client request.
class org.apache.ignite.binary.BinaryObjectException: Not enough data
to read the value [position=22, requiredBytes=4, remainingBytes=0]
at 
org.apache.ignite.internal.binary.streams.BinaryAbstractInputStream.ensureEnoughData(BinaryAbstractInputStream.java:305)
at 
org.apache.ignite.internal.binary.streams.BinaryAbstractInputStream.readInt(BinaryAbstractInputStream.java:127)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readInt(BinaryReaderExImpl.java:743)
at 
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheConfigurationSerializer.read(ClientCacheConfigurationSerializer.java:125)
at 
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheCreateWithConfigurationRequest.(ClientCacheCreateWithConfigurationRequest.java:45)
at 
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:333)
at 
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:220)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:119)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at 
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Re: Plugins documentation

[Prachi Garg]

Pavel,

Added the link.

-P

On Wed, Dec 6, 2017 at 12:14 PM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:

> Prachi, great job!
> Should we mention .NET plugins there?
> https://apacheignite-net.readme.io/docs/plugins
>
> On Wed, Dec 6, 2017 at 11:09 PM, Prachi Garg <pg...@gridgain.com> wrote:
>
> > Igniters,
> >
> > The ability to extend Ignite features using custom plugins has been
> > supported by Ignite since its early stages but was never documented.
> > Finally, I have put together the documentation for this feature -
> > https://apacheignite.readme.io/v2.3/docs/plugins
> >
> > Let me know if you have any questions :)
> >
> > -Prachi
> >
>

Plugins documentation

[Prachi Garg]

Igniters,

The ability to extend Ignite features using custom plugins has been
supported by Ignite since its early stages but was never documented.
Finally, I have put together the documentation for this feature -
https://apacheignite.readme.io/v2.3/docs/plugins

Let me know if you have any questions :)

-Prachi

Re: Thin Client Protocol documentation

[Prachi Garg]

Hi Pavel,

I am trying to use the OP_CACHE_CREATE_WITH_NAME operation, but can't get
it to work.  Digging deeper into the source code, it seems like I have to
provide a flag, string length, and position, in addition to the type code
and the actual string. Is that correct?

Here is the request I am sending to the server-

DataOutputStream out = new DataOutputStream(socket.getOutputStream());

// Message length
writeIntLittleEndian(24, out);

// Op code = OP_CACHE_CREATE_WITH_NAME
writeShortLittleEndian(1051, out);

// Request id
long reqId = 1;
writeLongLittleEndian(reqId, out);

// String (cache name)
writeByteLittleEndian(9, out); // Type code
writeByteLittleEndian(0, out); // Flag
writeIntLittleEndian(20, out); // String length
writeIntLittleEndian(0, out); // Position
out.writeUTF("myNewCache"); // Cache name

// Send request
out.flush();

But I get the following error on the server side.

[2017-12-04
17:27:39,421][ERROR][client-connector-#53][ClientListenerNioListener]
Failed to parse client request.
java.lang.StringIndexOutOfBoundsException: String index out of range: 2575
at java.lang.String.checkBounds(String.java:385)
at java.lang.String.(String.java:462)
at
org.apache.ignite.internal.binary.BinaryUtils.doReadString(BinaryUtils.java:1314)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.readString(BinaryReaderExImpl.java:1055)
at
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheCreateWithNameRequest.(ClientCacheCreateWithNameRequest.java:43)
at
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:318)
at
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:220)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:119)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

What am I missing here? Can you provide an example of how to send a
'String' type request?

-Prachi

On Mon, Dec 4, 2017 at 1:06 PM, Andrey Kornev 
wrote:

> Pavel,
>
> Thanks! While we're at it, are there any plans to add cluster-related
> operations? For example, I think it'd be nice to allow the thin clients to
> obtain a current topology snapshot. This would make it possible the clients
> to send requests directly to the affinity host for colocated computation.
> To make it even more useful, all server responses could optionally include
> the topology version the operation has been executed against. This would
> effectively give us a kind out-of-band topology change notification
> mechanism. This way the clients can detect a topology change and refresh
> the topology snapshot next time they need to compute affinity.
>
> Regards
> Andrey
> 
> From: Pavel Tupitsyn 
> Sent: Sunday, December 3, 2017 9:23 AM
> To: dev@ignite.apache.org
> Subject: Re: Thin Client Protocol documentation
>
> Hi Andrey,
>
> Compute and other APIs are certainly planned, cache is just a start.
> We intentionally limit the scope to actually release something in 2.4 and
> not delay it further.
>
> Adding operations to existing protocol is relatively easy.
> Current focus is to make sure that the protocol itself is solid and
> future-proof.
>
> Thanks,
> Pavel
>

Re: Thin Client Protocol documentation

[Prachi Garg]

Pavel,

How do you specify the flags (withSkipStore, withExpiryPolicy, etc..) in
bytes? Do you have a code for each of them?

On Sun, Dec 3, 2017 at 9:23 AM, Pavel Tupitsyn  wrote:

> Hi Andrey,
>
> Compute and other APIs are certainly planned, cache is just a start.
> We intentionally limit the scope to actually release something in 2.4 and
> not delay it further.
>
> Adding operations to existing protocol is relatively easy.
> Current focus is to make sure that the protocol itself is solid and
> future-proof.
>
> Thanks,
> Pavel
>

Re: Thin Client Protocol documentation

[Prachi Garg]

Pavel,

If the connection handshake fails, what should be the message length in the
response. When I try to fail the handshake, I get 32 as the message length.
Is this expected?

-Prachi

On Wed, Nov 29, 2017 at 8:20 AM, Pavel Tupitsyn <ptupit...@gridgain.com>
wrote:

> Hi Prachi,
>
> Flags parameter in all cache operations is reserved for things like
> withSkipStore, withExpiryPolicy, withKeepBinary, withNoRetries,
> withPartitionRecover.
> See methods in IgniteCache interface.
>
> Thanks,
> Pavel
>
> On Wed, Nov 29, 2017 at 7:10 PM, Prachi Garg <pg...@gridgain.com> wrote:
>
>> Hi Pavel,
>>
>> In the operation request, what does the 'flags' parameter mean?
>>
>>
>> Thanks,
>> -Prachi
>>
>> On Wed, Nov 29, 2017 at 5:27 AM, Pavel Tupitsyn <ptupit...@apache.org>
>> wrote:
>>
>>> Sergey, good point, done.
>>>
>>> On Wed, Nov 29, 2017 at 2:30 PM, Sergey Kozlov <skoz...@gridgain.com>
>>> wrote:
>>>
>>> > Pavel
>>> >
>>> > Could you update the page by following:
>>> >
>>> >  - String, date, UUID arrays allow to put NULL. Due to that every item
>>> in
>>> > the array written as type code byte (default item type or null type
>>> code) +
>>> > type data. It should be detailed explained (looks like that the table
>>> > should have an addtional column called for instance "nullable")
>>> >
>>> > -  UUID type takes 16 bytes length
>>> >
>>> > thanks
>>> >
>>> >
>>> > On Mon, Nov 27, 2017 at 4:37 PM, Sergey Kozlov <skoz...@gridgain.com>
>>> > wrote:
>>> >
>>> > > Pavel
>>> > >
>>> > > Thanks for explanations!
>>> > >
>>> > > On Mon, Nov 27, 2017 at 2:46 PM, Pavel Tupitsyn <
>>> ptupit...@apache.org>
>>> > > wrote:
>>> > >
>>> > >> Sergey,
>>> > >>
>>> > >> 1. Code table size does not affect anything, as I understand, so
>>> there
>>> > is
>>> > >> no reason to introduce an extra byte.
>>> > >> 2. We have object arrays (code 23), I forgot to mention them, fixed.
>>> > >> 3. Also forgot, see code 25 in the updated document.
>>> > >>
>>> > >> Also note that operation codes have been updated (grouped by
>>> purpose) as
>>> > >> part of https://issues.apache.org/jira/browse/IGNITE-6989.
>>> > >>
>>> > >> Thanks,
>>> > >> Pavel
>>> > >>
>>> > >> On Sun, Nov 26, 2017 at 9:54 PM, Sergey Kozlov <
>>> skoz...@gridgain.com>
>>> > >> wrote:
>>> > >>
>>> > >> > Pavel
>>> > >> >
>>> > >> > Thanks for the document and your efforts for new protocol. It was
>>> > really
>>> > >> > helpful for playing around the python thin client design.
>>> > >> >
>>> > >> > Could you explain some things that were still not clear for binary
>>> > >> object
>>> > >> > format:
>>> > >> >
>>> > >> > 1. What a reason to introduce separated type codes for arrays? Why
>>> > just
>>> > >> we
>>> > >> > can't use the following?
>>> > >> > *<1 byte universal array code>*
>>> > >> > *<1 byte primitive code>*
>>> > >> > *<4 bytes length>*
>>> > >> > **
>>> > >> >
>>> > >> > We get 1 byte overhead but save 10 bytes in the code table. For
>>> arrays
>>> > >> the
>>> > >> > overhead is really insignificant:10 longs array takes now
>>> 1+4+4*10=45
>>> > >> bytes
>>> > >> > vs 1+1+4+4*10=46 bytes for the approach
>>> > >> > Moreover for that appoach a new primitive code will be available
>>> for
>>> > >> using
>>> > >> > for array immediately.
>>> > >> >
>>> > >> > 2. Why the arrays force to use a selected type? For python
>>> there's no
>>> > >> > limitations to use different types across one array (list). Would
>>> be
>>> > >> good
>>> > >

Re: Thin Client Protocol documentation

[Prachi Garg]

Hi Pavel,

In the operation request, what does the 'flags' parameter mean?


Thanks,
-Prachi

On Wed, Nov 29, 2017 at 5:27 AM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:

> Sergey, good point, done.
>
> On Wed, Nov 29, 2017 at 2:30 PM, Sergey Kozlov <skoz...@gridgain.com>
> wrote:
>
> > Pavel
> >
> > Could you update the page by following:
> >
> >  - String, date, UUID arrays allow to put NULL. Due to that every item in
> > the array written as type code byte (default item type or null type
> code) +
> > type data. It should be detailed explained (looks like that the table
> > should have an addtional column called for instance "nullable")
> >
> > -  UUID type takes 16 bytes length
> >
> > thanks
> >
> >
> > On Mon, Nov 27, 2017 at 4:37 PM, Sergey Kozlov <skoz...@gridgain.com>
> > wrote:
> >
> > > Pavel
> > >
> > > Thanks for explanations!
> > >
> > > On Mon, Nov 27, 2017 at 2:46 PM, Pavel Tupitsyn <ptupit...@apache.org>
> > > wrote:
> > >
> > >> Sergey,
> > >>
> > >> 1. Code table size does not affect anything, as I understand, so there
> > is
> > >> no reason to introduce an extra byte.
> > >> 2. We have object arrays (code 23), I forgot to mention them, fixed.
> > >> 3. Also forgot, see code 25 in the updated document.
> > >>
> > >> Also note that operation codes have been updated (grouped by purpose)
> as
> > >> part of https://issues.apache.org/jira/browse/IGNITE-6989.
> > >>
> > >> Thanks,
> > >> Pavel
> > >>
> > >> On Sun, Nov 26, 2017 at 9:54 PM, Sergey Kozlov <skoz...@gridgain.com>
> > >> wrote:
> > >>
> > >> > Pavel
> > >> >
> > >> > Thanks for the document and your efforts for new protocol. It was
> > really
> > >> > helpful for playing around the python thin client design.
> > >> >
> > >> > Could you explain some things that were still not clear for binary
> > >> object
> > >> > format:
> > >> >
> > >> > 1. What a reason to introduce separated type codes for arrays? Why
> > just
> > >> we
> > >> > can't use the following?
> > >> > *<1 byte universal array code>*
> > >> > *<1 byte primitive code>*
> > >> > *<4 bytes length>*
> > >> > **
> > >> >
> > >> > We get 1 byte overhead but save 10 bytes in the code table. For
> arrays
> > >> the
> > >> > overhead is really insignificant:10 longs array takes now
> 1+4+4*10=45
> > >> bytes
> > >> > vs 1+1+4+4*10=46 bytes for the approach
> > >> > Moreover for that appoach a new primitive code will be available for
> > >> using
> > >> > for array immediately.
> > >> >
> > >> > 2. Why the arrays force to use a selected type? For python there's
> no
> > >> > limitations to use different types across one array (list). Would be
> > >> good
> > >> > to introduce a new type that will allow that. It could be look like
> > >> > following
> > >> > *<1 byte universal array code>*
> > >> > *<1 byte no common type code*> <-- this says that every item must
> > >> provide
> > >> > its date type code like it does regular primitive data
> > >> > *<4 bytes length>*
> > >> > *<1 byte item 0 type code>* <-- item provides its code
> > >> > **  <-- item provides its data
> > >> > *<1 byte item 1 type code>*
> > >> > **
> > >> > etc
> > >> >
> > >> > Also that allow to put nested arrays without changes in type code
> > table!
> > >> > For instance if we want to store 9 longs and 1 boolean it will take
> > >> > now 1+1+4+(1+9)*4+(1+1)=48
> > >> > bytes (vs 45 bytes to store as 10 longs as usual).
> > >> >
> > >> > 3. Ther's only one way to store a dictionary (key-value) structure
> as
> > >> value
> > >> > in the cache via Complex Object. But it looks like overcomplicated.
> I
> > >> > suppose to introduce a code for that
> > >> > *<1 byte key-value dictionary code>*
> > >> >
> > >> &

Activate/deactivate cluster through http-rest api

[Prachi Garg]

Engineers,

Any progress regarding this issue [1]?

[1]
https://issues.apache.org/jira/browse/IGNITE-5733?focusedCommentId=16225941=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16225941

Thanks,
-Prachi

Re: Thin Client Protocol documentation

[Prachi Garg]

Thanks Pavel! The document has good information. I'll create one on
readme.io; will also add some examples there.

On Wed, Nov 22, 2017 at 5:03 AM, Pavel Tupitsyn 
wrote:

> Igniters,
>
> I've put together a detailed description of our Thin Client protocol
> in form of IEP on wiki:
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 9+Thin+Client+Protocol
>
>
> To clarify:
> - Protocol implementation is in master (see ClientMessageParser class)
> - Protocol has not been released yet, so we are free to change anything
> - Protocol is only used by .NET Thin Client for now, but is supposed to be
> used from other languages by third party contributors
> - More operations will be added in future, this is a first set of them,
> cache-related
>
>
> Please review the document and let me know your thoughts.
> Is there anything missing or wrong?
>
> We should make sure that the foundation is solid and extensible.
>
>
> Thanks,
> Pavel
>

Re: Control.sh script and cluster activation

[Prachi Garg]

Guys,

I have added the documentation for Cluster Activation -
https://apacheignite.readme.io/docs/cluster-activation

While documenting, I noticed that the message printed on executing the
"control.sh --activate|deactivate" command is not giving me any useful
information. I can't tell if the cluster is active or not.
Similarly, the help message for "control.sh --help" is not very helpful :)

-P

On Tue, Aug 15, 2017 at 4:13 PM, Denis Magda  wrote:

> Add a documentation requirement. Ping me when the ticket is about to be
> closed.
>
> In the meanwhile, I’ll try to document the existing behavior.
>
> —
> Denis
>
> > On Aug 15, 2017, at 1:45 AM, Dmitriy Govorukhin <
> dmitriy.govoruk...@gmail.com> wrote:
> >
> > Folks,
> >
> > I created jira issue for the current discussion IGNITE-6064
> > , leave you comment
> > please.
> >
> > On Tue, Aug 15, 2017 at 11:32 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> >> Added one more suggestion below. BTW, if there is no ticket, let's
> create
> >> one and copy all the suggestions there.
> >>
> >> On Tue, Aug 15, 2017 at 1:13 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> >> wrote:
> >>
> >>> Guys,
> >>>
> >>> Where is the ticket for adding control.[sh|bat] script to the bin
> folder?
> >>> I cannot find any mention of it. Was there a discussion on the dev
> list?
> >>>
> >>> Here are the issues I am seeing with the script:
> >>>
> >>>   1. It could be named better. Perhaps the name "cluster-ops" or
> >>>   "cluster-switch" would be better. We should rename it in the next
> >> release.
> >>>   2. typing any bad command, e.g. "control bla" should provide a
> >>>   standard usage message explaining correct syntax (see any other
> >> command
> >>>   under bin folder)
> >>>   3. failure to connect to the cluster results in a long stack trace...
> >>>   instead, it should provide a standard error message, suggesting
> >> possible
> >>>   reasons for it.
> >>>
> >>> 4. Whenever trying to connect to a cluster, the script should print
> out a
> >> message "Connecting to ip-address:port ...". Otherwise, it looks like
> it is
> >> just hanging.
> >>
> >>
> >>> D.
> >>>
> >>> On Tue, Aug 15, 2017 at 12:59 AM, Dmitriy Govorukhin <
> >>> dmitriy.govoruk...@gmail.com> wrote:
> >>>
>  Valentin,
> 
>  We have jira issue for this IGNITE-5586
>  
> 
>  On Tue, Aug 15, 2017 at 10:56 AM, Dmitriy Govorukhin <
>  dmitriy.govoruk...@gmail.com> wrote:
> 
> >
> > Denis,
> >
> > 1. control.sh have help parameter. If you try enter ./control.sh
> >> --help,
> > result is an example of how to use it,
> > "Example: --host {ip} --port {port} --{activate/deactivate} or
> without
> > command --host {ip} --port {port} then will print status"
> >
> > 2. Visorcmd will start daemon node and join in topology, it is quite
>  long
> > time(as you know nodes joining in series) and requires resources.
> > Main goal was create some point for activation, fast and lightweight,
> > script does not start node.
> >
> > 3. Historically, the first name(control.sh - controls cluster
> > state active/inactive).  Have any idea for another name?
> >
> > On Tue, Aug 15, 2017 at 2:25 AM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> >> Agree that this is confusing. I think this functionality should be a
>  part
> >> of Visor CLI tool (likely a new command there).
> >>
> >> -Val
> >>
> >> On Mon, Aug 14, 2017 at 4:21 PM, Denis Magda 
>  wrote:
> >>
> >>> Dmitriy,
> >>>
> >>> I see you contributed control.sh script that activates a cluster
>  after a
> >>> restart. Honestly, I’m a bit confused by it:
> >>>
> >>> 1. How to use it? I could find out that there are some of the
>  parameters
> >>> but the ‘help’ is not implemented. Please fix this and provide a
> >>> description for every parameter you introduced.
> >>>
> >>> 2. Why did we decide to create a specific script for that? Why
> >> can’t
>  we
> >>> use existing visorcmd script?
> >>>
> >>> 3. Why the script called “control.sh”?
> >>>
> >>> —
> >>> Denis
> >>
> >
> >
> 
> >>>
> >>>
> >>
>
>

Re: Adding sqlline tool to Apache Ignite project

[Prachi Garg]

Here is the link for SQLLine documentation -
https://apacheignite-sql.readme.io/v2.1/docs/sqlline

-P

On Tue, Oct 17, 2017 at 11:54 AM, Denis Magda  wrote:

> Looks good to me. Prachi will help us documenting the tool usage:
> https://issues.apache.org/jira/browse/IGNITE-6656 <
> https://issues.apache.org/jira/browse/IGNITE-6656>
>
> However, I can’t conceive how to see a table structure (columns and their
> types, indexes with names and types) using SQLLine. I’ve tried !metadata
> with a variety of parameters but no luck. As for !indexes and !tables
> commands they just print out table names and secondary indexes omitting
> columns, indexes types and *primary indexes*. Considering that Ignite
> doesn’t support standard *describe* command I assumed SQLLine would help us
> out. But how do I do this with SQLLine?
>
> —
> Denis
>
> > On Oct 17, 2017, at 4:33 AM, Oleg Ostanin  wrote:
> >
> > New example build with sqlline:
> >
> > https://ci.ignite.apache.org/viewLog.html?buildId=894407;
> tab=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
> pareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp
> >
> >
> > On Wed, Oct 11, 2017 at 1:00 AM, Denis Magda  wrote:
> >
> >> Oleg,
> >>
> >> Looks good to me. Please consider the notes left in the ticket. I want
> us
> >> to prepare a script for Windows, review the language for help notice and
> >> errors, put together documentation. Prachi will be able to help with the
> >> editing and documentation.
> >>
> >> —
> >> Denis
> >>
> >>> On Oct 9, 2017, at 10:13 AM, Oleg Ostanin 
> wrote:
> >>>
> >>> New build with fixed argument parsing:
> >>> https://ci.ignite.apache.org/viewLog.html?buildId=882282;
> >> tab=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
> >> pareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp
> >>>
> >>> On Mon, Oct 9, 2017 at 5:38 PM, Denis Magda 
> wrote:
> >>>
>  I think it’s a must have for the ticket resolution.
> 
>  Denis
> 
>  On Monday, October 9, 2017, Anton Vinogradov <
> avinogra...@gridgain.com>
>  wrote:
> 
> > Any plans to have ignitesql.bat?
> >
> > On Mon, Oct 9, 2017 at 5:29 PM, Oleg Ostanin  > > wrote:
> >
> >> Another build with sqlline included:
> >> https://ci.ignite.apache.org/viewLog.html?buildId=881120;
> >> tab=artifacts=IgniteRelease_
> >> XxxFromMirrorIgniteRelease3Pre
> >> pareVote#!1rrb2,-wpvx2aopzexz,1esn4zrslm4po,-h8h0hn9vvvxp
> >>
> >> On Sun, Oct 8, 2017 at 5:11 PM, Denis Magda  > > wrote:
> >>
> >>> No more doubts on my side. +1 for Vladimir’s suggestion.
> >>>
> >>> Denis
> >>>
> >>> On Saturday, October 7, 2017, Dmitriy Setrakyan <
>  dsetrak...@apache.org
> > >
> >>> wrote:
> >>>
>  I now tend to agree with Vladimir. We should always require that
>  some
>  address is specified. The help menu should clearly state how to
> > connect
> >>> to
>  a localhost.
> 
>  D.
> 
>  On Sat, Oct 7, 2017 at 12:44 AM, Vladimir Ozerov <
> > voze...@gridgain.com 
>  >
>  wrote:
> 
> > Denis,
> >
> > Default Ignite configuration uses multicast, this is why you do
>  not
> >>> need
>  to
> > change anything. Ignite node is always both a server (listens)
>  and
> > a
>  client
> > (connects).
> >
> > This will not work for ignitesql, as this is a client. And in
>  real
> > deployments it will connect to remote nodes, not local. So the
> >> earlier
> >>> we
> > explain user how to do this, the better. This is why it should
>  not
> >> work
>  out
> > of the box connecting to 127.0.0.1. No magic for users please.
> >
> > This is what user will see (draft):
> >> ./ignitesql.sh
> >> Please specify the host: ignitesql.sh [host]; type --help for
> > more
> > information.
> >> ./ignitesql.sh 192.168.12.55
> >> Connected successfully.
> >
> > Again, specifying parameters manually is not poor UX. This is
> >> excellent
>  UX,
> > as user learns on his own how to connect to a node in 1 minute.
> > Most
> > command line tools work this way.
> >
> > сб, 7 окт. 2017 г. в 7:12, Dmitriy Setrakyan <
> > dsetrak...@apache.org 
>  >:
> >
> >> How does the binding happen? Can we bind to everything, like we
> > do
> >> in
> >> Ignite?
> >>
> >> On Fri, Oct 6, 2017 at 2:51 PM, Denis Magda  > 
>  > wrote:
> >>
> 

Re: documentation suggestions

[Prachi Garg]

WAL modes is documented -
https://apacheignite.readme.io/v2.2/docs/ignite-persistence-23#section-wal-modes

On Wed, Oct 4, 2017 at 2:07 PM, Denis Magda  wrote:

> Please see inline
>
> > On Oct 4, 2017, at 5:17 AM, Dmitriy Setrakyan 
> wrote:
> >
> > I would like to propose some changes to the Ignite documentation:
> >
> >   - Under Basic Concepts add the following pages:
> >  - "How to load data”
>
> This should go to “Data Loading” or Streaming sections that appear at the
> top of the doc. We have more room there once new SQL doc is released.
>
> >  - "SQL vs Scan"
> >  - "SQL vs Key-Value”
>
> Yes, it’s needed. The production readiness might be a good alternative to
> host the pages.
>
> >  - more?
> >   - For persistence section, add the following pages:
> >  - Write-Ahead-Log (WAL)
> > - BTW, I could not find WAL modes anywhere in documentation
> >  - Main Store (or Checkpointing)
>
> Presently, everything is in a good fit on a single persistence page. The
> navigation menu on the readme.io  is lengthy and might
> scary the one who sets off Ignite journey. It takes several seconds to
> scroll it down to brace for the volume you should absorb. Let’s release the
> new SQL doc and see how much space is free there before extracting pages
> out of the paragraphs. Also we can try out subpages.
>
> WAL modes documentation: https://issues.apache.org/jira/browse/IGNITE-6558
> 
>
> —
> Denis
>
> >  - Configuration
> >
> > Thoughts?
> >
> > D.
>
>

Re: [DISCUSS] Ignite Update Checker

[Prachi Garg]

Yes, I see in dev tools that calls to googleads and doubleclick are made
from Youtube.

On Fri, Sep 29, 2017 at 4:33 PM, Denis Magda <dma...@apache.org> wrote:

> I also did a global search on the Ignite website, but didn't find anything
> for googleads or doubleclick.
>
>
> Could you remove and add screencasts block temporary on your local
> deployment to see if the calls to commercial scripts reported by Cos appear
> in your Chrome dev toolkit?
>
> —
> Denis
>
>
> On Sep 29, 2017, at 3:56 PM, Prachi Garg <pg...@gridgain.com> wrote:
>
> We use the following scripts -
>
> https://platform.twitter.com/widgets.js - used on homepage to display
> tweets
> https://static.addtoany.com/menu/page.js - used on events page for social
> media sharing
> https://www.google-analytics.com/analytics.js
>
> I also did a global search on the Ignite website, but didn't find anything
> for googleads or doubleclick.
>
> -Prachi
>
>
> On Fri, Sep 29, 2017 at 11:03 AM, Denis Magda <dma...@gridgain.com> wrote:
>
>> That’s definitely worthwhile checking. Prachi, as the one who embedded
>> the screencast, would you check the theory?
>>
>> —
>> Denis
>>
>> On Sep 28, 2017, at 11:50 PM, Alexey Kuznetsov <akuznet...@apache.org>
>> wrote:
>>
>> Cos, Denis.
>>
>> I think it is because we have embedded videos (on YouTube).
>> Mauricio or Denis, please check my idea.
>>
>> On Fri, Sep 29, 2017 at 8:02 AM, Konstantin Boudnik <c...@apache.org>
>> wrote:
>>
>>> Sorry guys - I neglected the fact that our lists don't permit
>>> attachments. I have put the screenshot to an external server [1]
>>>
>>> [1] https://imgur.com/a/p9FJ9
>>>
>>> Thank you!
>>> --
>>>   With regards,
>>> 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 Thu, Sep 28, 2017 at 1:37 PM, Denis Magda <dma...@apache.org> wrote:
>>> > Cos,
>>> >
>>> > The screenshot was not attached. Could you share it some other way
>>> (google drive, etc.)? I’ve never seen any commercial on the site.
>>> >
>>> > —
>>> > Denis
>>> >
>>> >> On Sep 28, 2017, at 7:23 AM, Konstantin Boudnik <c...@apache.org>
>>> wrote:
>>> >>
>>> >> I don't see an issue with node version either.
>>> >>
>>> >> Just one more, and it might be slightly irrelevant, issue though... I
>>> looked at the Ignite's site and found the following ads and trackers (that
>>> are indeed getting disabled by my browser).
>>> >> Why are googleads or doubleclick are permitted?
>>> >>
>>> >>
>>> >>
>>> >> Thanks,
>>> >>   Cos
>>> >>
>>> >>
>>> >> --
>>> >>   With regards,
>>> >> 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, Sep 26, 2017 at 3:21 PM, Dmitriy Setrakyan <
>>> dsetrak...@apache.org <mailto:dsetrak...@apache.org>> wrote:
>>> >> On Tue, Sep 26, 2017 at 6:20 AM, Vladimir Ozerov <
>>> voze...@gridgain.com <mailto:voze...@gridgain.com>>
>>> >> wrote:
>>> >>
>>> >> > Folks,
>>> >> >
>>> >> > Can we add version of current node to web request? This way we will
>>> better
>>> >> > understand version distribution, what might help us with certain API
>>> >> > update/deprecate decisions
>>> >> > E.g. http://ignite.apache.org/latest.cgi=2.2.0 <
>>> http://ignite.apache.org/latest.cgi=2.2.0>
>>> >>
>>> >>
>>> >> Vladimir, I personally do not see a problem with that, as sending the
>>> >> current version to the update checker seems very innocent to me. At
>>> the
>>> >> same time, it will allow us to ex

Re: [DISCUSS] Ignite Update Checker

[Prachi Garg]

We use the following scripts -

https://platform.twitter.com/widgets.js - used on homepage to display tweets
https://static.addtoany.com/menu/page.js - used on events page for social
media sharing
https://www.google-analytics.com/analytics.js

I also did a global search on the Ignite website, but didn't find anything
for googleads or doubleclick.

-Prachi


On Fri, Sep 29, 2017 at 11:03 AM, Denis Magda  wrote:

> That’s definitely worthwhile checking. Prachi, as the one who embedded the
> screencast, would you check the theory?
>
> —
> Denis
>
> On Sep 28, 2017, at 11:50 PM, Alexey Kuznetsov 
> wrote:
>
> Cos, Denis.
>
> I think it is because we have embedded videos (on YouTube).
> Mauricio or Denis, please check my idea.
>
> On Fri, Sep 29, 2017 at 8:02 AM, Konstantin Boudnik 
> wrote:
>
>> Sorry guys - I neglected the fact that our lists don't permit
>> attachments. I have put the screenshot to an external server [1]
>>
>> [1] https://imgur.com/a/p9FJ9
>>
>> Thank you!
>> --
>>   With regards,
>> 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 Thu, Sep 28, 2017 at 1:37 PM, Denis Magda  wrote:
>> > Cos,
>> >
>> > The screenshot was not attached. Could you share it some other way
>> (google drive, etc.)? I’ve never seen any commercial on the site.
>> >
>> > —
>> > Denis
>> >
>> >> On Sep 28, 2017, at 7:23 AM, Konstantin Boudnik 
>> wrote:
>> >>
>> >> I don't see an issue with node version either.
>> >>
>> >> Just one more, and it might be slightly irrelevant, issue though... I
>> looked at the Ignite's site and found the following ads and trackers (that
>> are indeed getting disabled by my browser).
>> >> Why are googleads or doubleclick are permitted?
>> >>
>> >>
>> >>
>> >> Thanks,
>> >>   Cos
>> >>
>> >>
>> >> --
>> >>   With regards,
>> >> 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, Sep 26, 2017 at 3:21 PM, Dmitriy Setrakyan <
>> dsetrak...@apache.org > wrote:
>> >> On Tue, Sep 26, 2017 at 6:20 AM, Vladimir Ozerov > >
>> >> wrote:
>> >>
>> >> > Folks,
>> >> >
>> >> > Can we add version of current node to web request? This way we will
>> better
>> >> > understand version distribution, what might help us with certain API
>> >> > update/deprecate decisions
>> >> > E.g. http://ignite.apache.org/latest.cgi=2.2.0 <
>> http://ignite.apache.org/latest.cgi=2.2.0>
>> >>
>> >>
>> >> Vladimir, I personally do not see a problem with that, as sending the
>> >> current version to the update checker seems very innocent to me. At the
>> >> same time, it will allow us to examine the usage of each release and
>> make
>> >> decisions about dropping backward compatibility or spotting bugs for a
>> >> certain release.
>> >>
>> >> Cos, Raul, any thoughts?
>> >>
>> >>
>> >> >
>> >> >
>> >> > Vladimir.
>> >> >
>> >> > On Fri, Sep 8, 2017 at 7:06 AM, Dmitriy Setrakyan <
>> dsetrak...@apache.org >
>> >> > wrote:
>> >> >
>> >> > > I think it is safe to assume at this point that everyone is in
>> general
>> >> > > agreement, since there are no active objections.
>> >> > >
>> >> > > I have filed a ticket for the 2.3 release. Let's try to make it
>> happen:
>> >> > > https://issues.apache.org/jira/browse/IGNITE-6305 <
>> https://issues.apache.org/jira/browse/IGNITE-6305>
>> >> > >
>> >> > > D.
>> >> > >
>> >> > > On Sat, Aug 26, 2017 at 3:06 PM, Dmitriy Setrakyan <
>> >> > dsetrak...@apache.org >
>> >> > > wrote:
>> >> > >
>> >> > > >
>> >> > > >
>> >> > > > On Sat, Aug 26, 2017 at 3:22 AM, Raúl Kripalani <
>> raul@evosent.com >
>> >> > > > wrote:
>> >> > > >
>> >> > > >> Yeah, I guess that's doable as well and requires less management
>> >> > effort
>> >> > > >> than my suggestion. We could use events [1] to store payload
>> data
>> >> > (e.g.
>> >> > > >> IP,
>> >> > > >> version, etc.)
>> >> > > >
>> >> > > >
>> >> > > > Yes, we could use events or some other similar API provided by
>> GA.
>> >> > > >
>> >> > > >
>> >> > > >> What the download page CGI developed in? PHP?
>> >> > > >>
>> >> > > >
>> >> > > > To be honest, no clue. I guess someone in the community can
>> figure it
>> >> > > out:
>> >> > > > https://svn.apache.org/repos/asf/ignite/site/trunk/download.html
>> 
>> >> > > >
>> >> > > >

[jira] [Created] (IGNITE-6361) Add Meta descriptions on Ignite website pages

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-6361:
---

 Summary: Add Meta descriptions on Ignite website pages
 Key: IGNITE-6361
 URL: https://issues.apache.org/jira/browse/IGNITE-6361
 Project: Ignite
  Issue Type: Task
Reporter: Prachi Garg
Assignee: Prachi Garg
 Fix For: 2.2


Determine which pages need meta descriptions and create them. Meta descriptions 
should be unique and created to draw users in from the SERPs.



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

Re: How to configure ignite-jcl and Ignite-slf4j logger

[Prachi Garg]

Valentin, Nikolai,

I have published my example on github -
https://github.com/pgarg/myIgniteExamples

On Mon, Sep 4, 2017 at 7:57 PM, Rishi Yagnik <rishiyag...@gmail.com> wrote:

> I have configured log4j, log4j-2 in our environment, can share additional
> details here if you need it.
>
> On Mon, Sep 4, 2017 at 11:54 AM, Nikolai Tikhonov <ntikho...@apache.org>
> wrote:
>
>> Prachi,
>>
>> I've published on github example with configured JCL logger. Please, have
>> a
>> look: https://github.com/TikhonovNikolay/jcl-ignite-example
>>
>> On Sat, Sep 2, 2017 at 12:36 AM, Prachi Garg <pg...@gridgain.com> wrote:
>>
>> > Yes, I tried using it, but strangely this is the output I get when use
>> > -DIGNITE_QUIET=false
>> > ( I set this property in Idea ->Run -> Edit Configurations -> VM
>> options)
>> >
>> > log4j:WARN No appenders could be found for logger
>> > (org.apache.ignite.internal.util.typedef.G).
>> > log4j:WARN Please initialize the log4j system properly.
>> > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig
>> for
>> > more info.
>> > Sep 01, 2017 2:33:07 PM java.util.logging.LogManager$RootLogger log
>> > SEVERE: Failed to resolve default logging config file:
>> > config/java.util.logging.properties
>> > class org.apache.ignite.internal.GridLoggerProxy
>> >
>> > Process finished with exit code 0
>> >
>> >
>> > On Fri, Sep 1, 2017 at 2:30 PM, Valentin Kulichenko <
>> > valentin.kuliche...@gmail.com> wrote:
>> >
>> > > Prachi,
>> > >
>> > > It looks like you're running in quiet mode. Did you try to set
>> > > -DIGNITE_QUIET=false
>> > > system property?
>> > >
>> > > -Val
>> > >
>> > > On Fri, Sep 1, 2017 at 10:43 AM, Prachi Garg <pg...@gridgain.com>
>> wrote:
>> > >
>> > > > Nikolai,
>> > > >
>> > > > I have specified 'gridlogger' property in 'IgniteConfiguration', but
>> > > looks
>> > > > like it does not get instantiated.
>> > > >
>> > > > > > > > class="org.apache.ignite.configuration.IgniteConfiguration">
>> > > >
>> > > > 
>> > > > 
>> > > > 
>> > > > 
>> > > > > > > > value="/Users/prachig/myexamples/config/ignite-log4j.xml"/>
>> > > > 
>> > > > 
>> > > > 
>> > > > 
>> > > >
>> > > > 
>> > > > ...
>> > > >
>> > > > 
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On Fri, Sep 1, 2017 at 10:16 AM, Nikolay Tikhonov <
>> > > ntikho...@gridgain.com>
>> > > > wrote:
>> > > >
>> > > > > Hi Denis,
>> > > > >
>> > > > > JCL it's wrapper for logging system (similar sl4j) which can be
>> used
>> > > > > together with log4j. I guess that JavaDoc correct.
>> > > > >
>> > > > > On Fri, Sep 1, 2017 at 5:40 PM, Denis Magda <dma...@apache.org>
>> > wrote:
>> > > > >
>> > > > > > Nikolai,
>> > > > > >
>> > > > > > Looking at JCL documentation I see the usage of Log4j together
>> with
>> > > > JCL:
>> > > > > >
>> > > > > > * 
>> > > > > > *  ...
>> > > > > > *  property name="gridLogger"
>> > > > > > *  bean class="org.apache.ignite.
>> > > logger.jcl.JclLogger"
>> > > > > > *  constructor-arg type="org.apache.commons.
>> > > > > > logging.Log"
>> > > > > > *  bean class="org.apache.commons.
>> > > > > > logging.impl.Log4JLogger"
>> > > > > > *  constructor-arg
>> type="java.lang.String"
>> > > > > > value="config/ignite-log4j.xml"/
>> > > > > > *  /bean
>> > > > > > *  /constructor-arg
>> > > > > > 

Re: How to configure ignite-jcl and Ignite-slf4j logger

[Prachi Garg]

Yes, I tried using it, but strangely this is the output I get when use
-DIGNITE_QUIET=false
( I set this property in Idea ->Run -> Edit Configurations -> VM options)

log4j:WARN No appenders could be found for logger
(org.apache.ignite.internal.util.typedef.G).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
Sep 01, 2017 2:33:07 PM java.util.logging.LogManager$RootLogger log
SEVERE: Failed to resolve default logging config file:
config/java.util.logging.properties
class org.apache.ignite.internal.GridLoggerProxy

Process finished with exit code 0


On Fri, Sep 1, 2017 at 2:30 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Prachi,
>
> It looks like you're running in quiet mode. Did you try to set
> -DIGNITE_QUIET=false
> system property?
>
> -Val
>
> On Fri, Sep 1, 2017 at 10:43 AM, Prachi Garg <pg...@gridgain.com> wrote:
>
> > Nikolai,
> >
> > I have specified 'gridlogger' property in 'IgniteConfiguration', but
> looks
> > like it does not get instantiated.
> >
> >  > class="org.apache.ignite.configuration.IgniteConfiguration">
> >
> > 
> > 
> > 
> > 
> >  > value="/Users/prachig/myexamples/config/ignite-log4j.xml"/>
> > 
> > 
> > 
> > 
> >
> > 
> > ...
> >
> > 
> >
> >
> >
> >
> > On Fri, Sep 1, 2017 at 10:16 AM, Nikolay Tikhonov <
> ntikho...@gridgain.com>
> > wrote:
> >
> > > Hi Denis,
> > >
> > > JCL it's wrapper for logging system (similar sl4j) which can be used
> > > together with log4j. I guess that JavaDoc correct.
> > >
> > > On Fri, Sep 1, 2017 at 5:40 PM, Denis Magda <dma...@apache.org> wrote:
> > >
> > > > Nikolai,
> > > >
> > > > Looking at JCL documentation I see the usage of Log4j together with
> > JCL:
> > > >
> > > > * 
> > > > *  ...
> > > > *  property name="gridLogger"
> > > > *  bean class="org.apache.ignite.
> logger.jcl.JclLogger"
> > > > *  constructor-arg type="org.apache.commons.
> > > > logging.Log"
> > > > *  bean class="org.apache.commons.
> > > > logging.impl.Log4JLogger"
> > > > *  constructor-arg type="java.lang.String"
> > > > value="config/ignite-log4j.xml"/
> > > > *  /bean
> > > > *  /constructor-arg
> > > > *  /bean
> > > > *  /property
> > > > *  ...
> > > > * 
> > > >
> > > >
> > > > or
> > > >
> > > > * And the same configuration if you'd like to configure Ignite in
> your
> > > > code:
> > > > * 
> > > > *  IgniteConfiguration cfg = new IgniteConfiguration();
> > > > *  ...
> > > > *  IgniteLogger log = new JclLogger(new
> Log4JLogger("config/ignite-
> > > > log4j.xml"));
> > > > *  ...
> > > > *  cfg.setGridLogger(log);
> > > > * 
> > > >
> > > >
> > > > Is it wrong? Could you fix the Java Doc in a proper way?
> > > >
> > > >
> > > > > On Sep 1, 2017, at 3:12 AM, Nikolai Tikhonov <ntikho...@apache.org
> >
> > > > wrote:
> > > > >
> > > > > Hello Prachi!
> > > > >
> > > > > You need to set gridLogger property in IgniteConfiguration and
> remove
> > > > ignite-log4j dependency from POM file.
> > > > >
> > > > > For example for Sl4j logger:
> > > > >
> > > > > igniteConfiguration.setGridLogger(new Slf4jLogger());
> > > > >
> > > > > and for Jc logger:
> > > > >
> > > > > igniteConfiguration.setGridLogger(new JclLogger());
> > > > >
> > > > > On Fri, Sep 1, 2017 at 2:44 AM, Prachi Garg <pg...@gridgain.com
> > >  > > > pg...@gridgain.com>> wrote:
> > > > > Engineers,
> > > > >
> > > > > In the attempt to document loggers supported by Ignite, I am
> having

Re: How to configure ignite-jcl and Ignite-slf4j logger

[Prachi Garg]

Nikolai,

I have specified 'gridlogger' property in 'IgniteConfiguration', but looks
like it does not get instantiated.














...






On Fri, Sep 1, 2017 at 10:16 AM, Nikolay Tikhonov <ntikho...@gridgain.com>
wrote:

> Hi Denis,
>
> JCL it's wrapper for logging system (similar sl4j) which can be used
> together with log4j. I guess that JavaDoc correct.
>
> On Fri, Sep 1, 2017 at 5:40 PM, Denis Magda <dma...@apache.org> wrote:
>
> > Nikolai,
> >
> > Looking at JCL documentation I see the usage of Log4j together with JCL:
> >
> > * 
> > *  ...
> > *  property name="gridLogger"
> > *  bean class="org.apache.ignite.logger.jcl.JclLogger"
> > *  constructor-arg type="org.apache.commons.
> > logging.Log"
> > *  bean class="org.apache.commons.
> > logging.impl.Log4JLogger"
> > *  constructor-arg type="java.lang.String"
> > value="config/ignite-log4j.xml"/
> > *  /bean
> > *  /constructor-arg
> > *  /bean
> > *  /property
> > *  ...
> > * 
> >
> >
> > or
> >
> > * And the same configuration if you'd like to configure Ignite in your
> > code:
> > * 
> > *  IgniteConfiguration cfg = new IgniteConfiguration();
> > *  ...
> > *  IgniteLogger log = new JclLogger(new Log4JLogger("config/ignite-
> > log4j.xml"));
> > *  ...
> > *  cfg.setGridLogger(log);
> > * 
> >
> >
> > Is it wrong? Could you fix the Java Doc in a proper way?
> >
> >
> > > On Sep 1, 2017, at 3:12 AM, Nikolai Tikhonov <ntikho...@apache.org>
> > wrote:
> > >
> > > Hello Prachi!
> > >
> > > You need to set gridLogger property in IgniteConfiguration and remove
> > ignite-log4j dependency from POM file.
> > >
> > > For example for Sl4j logger:
> > >
> > > igniteConfiguration.setGridLogger(new Slf4jLogger());
> > >
> > > and for Jc logger:
> > >
> > > igniteConfiguration.setGridLogger(new JclLogger());
> > >
> > > On Fri, Sep 1, 2017 at 2:44 AM, Prachi Garg <pg...@gridgain.com
>  > pg...@gridgain.com>> wrote:
> > > Engineers,
> > >
> > > In the attempt to document loggers supported by Ignite, I am having a
> > hard
> > > time configuring ignite-jcl and ignite-slf4j (I could configure log4j
> and
> > > log4j2). I don't see the log message on my console when I use
> ignite-jcl
> > or
> > > ignite-slf4j.
> > >
> > >  Below is the configuration and sample code I am using:
> > >
> > > *ignite-log4j.xml*
> > >
> > > 
> > >  > > xmlns:log4j='http://jakarta.apache.org/log4j/ <
> > http://jakarta.apache.org/log4j/>'>
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > >
> > >
> > > *Maven dependency -*
> > >
> > > 
> > > org.apache.ignite
> > > ignite-log4j
> > > 2.1.0
> > > 
> > >
> > > 
> > > org.apache.ignite
> > > ignite-jcl
> > > 2.1.0
> > > 
> > >
> > >
> > > *Configuration for JCL ( as specified in javadoc)- *
> > >
> > > 
> > > 
> > > 
> > > 
> > >  > > value="/Users/prachig/myexamples/config/ignite-log4j.xml"/>
> > > 
> > > 
> > > 
> > > 
> > >
> > >
> > > *Sample code I am using- *
> > >
> > > public class LoggerExample {
> > > public static void main(String[] args) throws IgniteException {
> > > try (Ignite ignite =
> > > Ignition.start("/Users/prachig/myexamples/config/cluster-config.xml"))
> > > {
> > > ignite.log().info("Info Message 1 Logged !!!");
> > > ignite.log().info("Info Message 2 Logged !!!");
> > >
> > > System.out.println(ignite.log().getClass());
> > >

How to configure ignite-jcl and Ignite-slf4j logger

[Prachi Garg]

Engineers,

In the attempt to document loggers supported by Ignite, I am having a hard
time configuring ignite-jcl and ignite-slf4j (I could configure log4j and
log4j2). I don't see the log message on my console when I use ignite-jcl or
ignite-slf4j.

 Below is the configuration and sample code I am using:

*ignite-log4j.xml*



















*Maven dependency -*


org.apache.ignite
ignite-log4j
2.1.0



org.apache.ignite
ignite-jcl
2.1.0



*Configuration for JCL ( as specified in javadoc)- *












*Sample code I am using- *

public class LoggerExample {
public static void main(String[] args) throws IgniteException {
try (Ignite ignite =
Ignition.start("/Users/prachig/myexamples/config/cluster-config.xml"))
{
ignite.log().info("Info Message 1 Logged !!!");
ignite.log().info("Info Message 2 Logged !!!");

System.out.println(ignite.log().getClass());
}
}
}

*Output*

/Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/bin/java
-Didea.launcher.port=7535
"-Didea.launcher.bin.path=/Applications/IntelliJ IDEA
CE.app/Contents/bin" -Dfile.encoding=UTF-8 -classpath

Re: Ignite Add-on/Extension Request: Please add GA Grid (beta) to Ignite website

[Prachi Garg]

Turik,

GA Grid is added to the "Addons and Related Solutions" section of the
Ignite website - https://ignite.apache.org/addons.html

Thank you for your contribution!

-P

On Thu, Aug 17, 2017 at 1:38 PM, Denis Magda  wrote:

> Hi Turik,
>
> Sure, we will do this with pleasure.
>
> Prachi, could you add the component to the mentioned page?
>
> —
> Denis
>
> > On Aug 16, 2017, at 9:16 PM, techbysample  wrote:
> >
> > Forum Admin,
> >
> > Please add project:
> >
> > GA Grid (beta): Distributive in Memory Genetic Algorithm component for
> > Ignite
> >
> > to "Addons and Extensions" section of Apache Ignite website:
> >
> > https://ignite.apache.org/addons.html
> >
> >  com/file/n20947/GAGrid_Overview.png>
> >
> > (F)itness Calculation, (C)rossover, and (M)utation operations are
> modeled as
> > a ComputeTask for distributive behavior. The ComputeTask is split into
> > multiple ComputeJobs, (ie: Fn,Cn,Mn) assigned to respective nodes, and
> > executed in parallel.
> >
> > All of these ComputeTasks leverage Apache Ignite's Affinity Colocation to
> > route ComputeJobs to respective nodes where Chromosomes are stored in
> cache.
> >
> > Additional information about GA Grid (beta) found here:
> >
> > https://github.com/techbysample/gagrid
> >
> > Please advise.
> >
> > Best,
> > Turik Campbell
> >
> >
> >
> > --
> > View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/Ignite-Add-on-Extension-
> Request-Please-add-GA-Grid-beta-to-Ignite-website-tp20947.html
> > Sent from the Apache Ignite Developers mailing list archive at
> Nabble.com.
>
>

Re: SQL Getting Started Guide

[Prachi Garg]

https://apacheignite.readme.io/docs/distributed-ddl#section-create-table
has examples for template and other extended parameters. The Extended
Parameters section explains how to register a template.

On Mon, Aug 21, 2017 at 5:19 PM, Dmitriy Setrakyan <d...@gridgain.com> wrote:

> Prachi, is there an example for a template file? Is there an example of how
> a template should be registered? Is there an example of how other extended
> parameters should be configured, i.e. a sample CREATE TABLE command?
>
> On Mon, Aug 21, 2017 at 5:15 PM, Prachi Garg <pg...@gridgain.com> wrote:
>
> > Template syntax is documented here -
> > https://apacheignite.readme.io/docs/distributed-ddl#
> > section-extended-parameters
> >
> > I've added a brief explanation on the SQL page (on the website) as well.
> >
> > On Mon, Aug 21, 2017 at 4:40 PM, Dmitriy Setrakyan <d...@gridgain.com>
> wrote:
> >
> > > Nikita,
> > >
> > > Thanks for checking. No, this is not on purpose.
> > >
> > > Denis, do we have the template syntax documented anywhere?
> > >
> > > D.
> > >
> > > On Mon, Aug 21, 2017 at 9:42 AM, Nikita Ivanov <nivano...@gmail.com>
> > > wrote:
> > >
> > > > I looked briefly and I couldn't find any explanation on "template" at
> > > all -
> > > > the only unique caveat apart from standard SQL. Is this on purpose?
> > > >
> > > > --
> > > > Nikita Ivanov
> > > >
> > > >
> > > > On Mon, Aug 21, 2017 at 9:36 AM, Prachi Garg <pg...@gridgain.com>
> > wrote:
> > > >
> > > > > Igor, Pavel
> > > > >
> > > > > On the website[1], I have added SQL, JDBC, ODBC, and Java API
> > examples
> > > > for
> > > > > DDL,
> > > > > DML and queries . I could not find DDL examples for .NET and C++ in
> > the
> > > > > documentation.  Please add the missing code snippets for .NET and
> C++
> > > > APIs
> > > > > taking SQL syntax from the Java API example.
> > > > >
> > > > > [1] https://ignite.apache.org/features/sql.html
> > > > >
> > > > > On Mon, Aug 21, 2017 at 3:28 AM, Igor Sapego <isap...@apache.org>
> > > wrote:
> > > > >
> > > > > > Prachi,
> > > > > >
> > > > > > Yeah, looks good. I've added creation of "Person" table to
> > > > documentation,
> > > > > > so take a look please.
> > > > > >
> > > > > > Best Regards,
> > > > > > Igor
> > > > > >
> > > > > > On Fri, Aug 18, 2017 at 10:29 PM, Prachi Garg <
> pg...@gridgain.com>
> > > > > wrote:
> > > > > >
> > > > > > > Hi Igor,
> > > > > > >
> > > > > > > The getting started guide is missing an example oh how to
> create
> > a
> > > > > Person
> > > > > > > table (under ODBC tab).
> > > > > > > https://apacheignite.readme.io/docs/getting-started-sql#
> > > > > > > section-create-tables
> > > > > > >
> > > > > > > I am trying to put one on the website. Does the following look
> > ok?
> > > > > > >
> > > > > > > // Create table based on PARTITIONED template with one backup
> > > > > > > SQLCHAR query[] = "CREATE TABLE Person ( "
> > > > > > > "id LONG, name VARCHAR, city_id LONG "
> > > > > > > "PRIMARY KEY (id, city_id)) "
> > > > > > > "WITH \"backups=1, affinityKey=city_id\"";
> > > > > > > SQLSMALLINT queryLen = static_cast(
> sizeof(query));
> > > > > > >
> > > > > > > SQLRETURN ret = SQLExecDirect(stmt, query, queryLen);
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Aug 18, 2017 at 12:09 PM, Denis Magda <
> dma...@apache.org
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Igor, thanks a lot. Appreciate this!
> > > > > > > >
> > > > > > > > —
> > > > > > > > Denis
> > > > > > > >
> > > > > > > > >

Re: SQL Getting Started Guide

[Prachi Garg]

Igor, Pavel

On the website[1], I have added SQL, JDBC, ODBC, and Java API examples for DDL,
DML and queries . I could not find DDL examples for .NET and C++ in the
documentation.  Please add the missing code snippets for .NET and C++ APIs
taking SQL syntax from the Java API example.

[1] https://ignite.apache.org/features/sql.html

On Mon, Aug 21, 2017 at 3:28 AM, Igor Sapego <isap...@apache.org> wrote:

> Prachi,
>
> Yeah, looks good. I've added creation of "Person" table to documentation,
> so take a look please.
>
> Best Regards,
> Igor
>
> On Fri, Aug 18, 2017 at 10:29 PM, Prachi Garg <pg...@gridgain.com> wrote:
>
> > Hi Igor,
> >
> > The getting started guide is missing an example oh how to create a Person
> > table (under ODBC tab).
> > https://apacheignite.readme.io/docs/getting-started-sql#
> > section-create-tables
> >
> > I am trying to put one on the website. Does the following look ok?
> >
> > // Create table based on PARTITIONED template with one backup
> > SQLCHAR query[] = "CREATE TABLE Person ( "
> > "id LONG, name VARCHAR, city_id LONG "
> > "PRIMARY KEY (id, city_id)) "
> > "WITH \"backups=1, affinityKey=city_id\"";
> > SQLSMALLINT queryLen = static_cast(sizeof(query));
> >
> > SQLRETURN ret = SQLExecDirect(stmt, query, queryLen);
> >
> >
> > On Fri, Aug 18, 2017 at 12:09 PM, Denis Magda <dma...@apache.org> wrote:
> >
> > > Igor, thanks a lot. Appreciate this!
> > >
> > > —
> > > Denis
> > >
> > > > On Aug 18, 2017, at 8:56 AM, Igor Sapego <isap...@apache.org> wrote:
> > > >
> > > > I've checked ODBC snippets and fixed all found issues.
> > > >
> > > > Best Regards,
> > > > Igor
> > > >
> > > > On Thu, Aug 17, 2017 at 11:16 PM, Denis Magda <dma...@apache.org>
> > wrote:
> > > >
> > > >> Igor,
> > > >>
> > > >> Would you mind helping us to test the snippets? I do believe it will
> > > take
> > > >> you a couple of minutes since the environment is set up on your
> side.
> > > >>
> > > >> —
> > > >> Denis
> > > >>
> > > >>> On Aug 17, 2017, at 5:37 AM, Igor Sapego <isap...@apache.org>
> wrote:
> > > >>>
> > > >>> Akmal,
> > > >>>
> > > >>> I work on the ODBC driver and would be glad to help. You can send
> > > >>> mails with your requests to devlist and I will try to help as much
> > as I
> > > >>> can.
> > > >>>
> > > >>> Best Regards,
> > > >>> Igor
> > > >>>
> > > >>> On Thu, Aug 17, 2017 at 3:28 PM, Akmal Chaudhri <
> > > >> akmal.chaud...@gridgain.com
> > > >>>> wrote:
> > > >>>
> > > >>>> When I have the opportunity to test the ODBC code and ensure that
> it
> > > >>>> performs, I will add it to GH. At the moment, just snippets exist.
> > If
> > > >>>> anyone can assist with this, I would appreciate it, as I have no
> > > >> experience
> > > >>>> with ODBC. I made some efforts to build the ODBC driver and have
> had
> > > >> some
> > > >>>> success on Windows and Linux, but have been unable to run any C++
> > > code.
> > > >>>>
> > > >>>> On 16 August 2017 at 21:41, Denis Magda <dma...@apache.org>
> wrote:
> > > >>>>
> > > >>>>> Igniters,
> > > >>>>>
> > > >>>>> The SQL getting started guide is ready and published:
> > > >>>>> https://apacheignite.readme.io/v2.1/docs/getting-started-sql
> > > >>>>>
> > > >>>>> Akmal thanks for your efforts and please apply the following
> minor
> > > >>>> changes:
> > > >>>>> * Add ODBC source files to your GitHub project.
> > > >>>>> * Add a flat SQL file (script) to the same project that will
> > include
> > > >> all
> > > >>>>> the pure SQL statements used in the guide.
> > > >>>>>
> > > >>>>> Basing on this guide I’ve prepared and release a guide for
> DBeaver
> > > 

Re: SQL Getting Started Guide

[Prachi Garg]

Hi Igor,

The getting started guide is missing an example oh how to create a Person
table (under ODBC tab).
https://apacheignite.readme.io/docs/getting-started-sql#section-create-tables

I am trying to put one on the website. Does the following look ok?

// Create table based on PARTITIONED template with one backup
SQLCHAR query[] = "CREATE TABLE Person ( "
"id LONG, name VARCHAR, city_id LONG "
"PRIMARY KEY (id, city_id)) "
"WITH \"backups=1, affinityKey=city_id\"";
SQLSMALLINT queryLen = static_cast(sizeof(query));

SQLRETURN ret = SQLExecDirect(stmt, query, queryLen);


On Fri, Aug 18, 2017 at 12:09 PM, Denis Magda  wrote:

> Igor, thanks a lot. Appreciate this!
>
> —
> Denis
>
> > On Aug 18, 2017, at 8:56 AM, Igor Sapego  wrote:
> >
> > I've checked ODBC snippets and fixed all found issues.
> >
> > Best Regards,
> > Igor
> >
> > On Thu, Aug 17, 2017 at 11:16 PM, Denis Magda  wrote:
> >
> >> Igor,
> >>
> >> Would you mind helping us to test the snippets? I do believe it will
> take
> >> you a couple of minutes since the environment is set up on your side.
> >>
> >> —
> >> Denis
> >>
> >>> On Aug 17, 2017, at 5:37 AM, Igor Sapego  wrote:
> >>>
> >>> Akmal,
> >>>
> >>> I work on the ODBC driver and would be glad to help. You can send
> >>> mails with your requests to devlist and I will try to help as much as I
> >>> can.
> >>>
> >>> Best Regards,
> >>> Igor
> >>>
> >>> On Thu, Aug 17, 2017 at 3:28 PM, Akmal Chaudhri <
> >> akmal.chaud...@gridgain.com
>  wrote:
> >>>
>  When I have the opportunity to test the ODBC code and ensure that it
>  performs, I will add it to GH. At the moment, just snippets exist. If
>  anyone can assist with this, I would appreciate it, as I have no
> >> experience
>  with ODBC. I made some efforts to build the ODBC driver and have had
> >> some
>  success on Windows and Linux, but have been unable to run any C++
> code.
> 
>  On 16 August 2017 at 21:41, Denis Magda  wrote:
> 
> > Igniters,
> >
> > The SQL getting started guide is ready and published:
> > https://apacheignite.readme.io/v2.1/docs/getting-started-sql
> >
> > Akmal thanks for your efforts and please apply the following minor
>  changes:
> > * Add ODBC source files to your GitHub project.
> > * Add a flat SQL file (script) to the same project that will include
> >> all
> > the pure SQL statements used in the guide.
> >
> > Basing on this guide I’ve prepared and release a guide for DBeaver
> SQL
> > tool:
> > https://apacheignite-tools.readme.io/docs/dbeaver
> >
> > —
> > Denis
> >
> > On Aug 11, 2017, at 3:17 PM, Denis Magda  wrote:
> >
> > Akmal,
> >
> > Good start! Please consider the following feedback:
> >
> > 1. Connectivity section. Emphasize that ignite-core.jar has to be
> >> copied
> > to the classpath of an app or tool and give a link to more advanced
> >> JDBC
> > Thin driver documentation if the one needs more details. Probably,
>  similar
> > steps should be brought up for the ODBC once it’s ready.
> >
> > 2. Make the first letters of city and people tables uppercase: city
> ->
> > City, people -> People
> >
> > 3. Rename INSERT section to “Inserting Data”, SELECT to “Querying
> >> Data”,
> > UPDATE -> “Modifying Data”, DELETE to “Removing Data” or to better
> > alternatives.
> >
> > 4. Show how to insert at least 2 cities and 5 people in the INSERT
>  section.
> >
> > —
> > Denis
> >
> > On Aug 11, 2017, at 10:42 AM, Akmal Chaudhri <
>  akmal.chaud...@gridgain.com>
> > wrote:
> >
> > Denis, All
> >
> > I have made some progress with the documentation:
> >
> > https://apacheignite.readme.io/v2.1/docs/getting-started-sql <
> > https://apacheignite.readme.io/v2.1/docs/getting-started-sql>
> >
> > ODBC connectivity and examples are missing, but should be completed
> >> very
> > soon.
> >
> > Community feedback welcome.
> >
> > Thanks.
> >
> > On 31 July 2017 at 19:02, Denis Magda  > mailto:dma...@apache.org >> wrote:
> > Igniters,
> >
> > There is a lot of SQL related documentation available for Ignite.
>  However,
> > the one can get lost in it when he/she does her first steps on a
> >> learning
> > path. It’s time to simplify these are first steps with a clear and
> > straightforward getting started guide. I’ve put the requirements into
>  this
> > JIRA ticket:
> > https://issues.apache.org/jira/browse/IGNITE-5886 <
> > https://issues.apache.org/jira/browse/IGNITE-5886>
> >
> > Please share your thoughts in JIRA or in this discussion.
> >
> > Akmal, who perfected his technical writer skills 

Re: Ignite Add-on/Extension Request: Please add GA Grid (beta) to Ignite website

[Prachi Garg]

Turik,

Thanks for you contribution. I will add it to the website early next week.

-P

On Fri, Aug 18, 2017 at 3:57 AM, techbysample  wrote:

> Dennis/Prachi,
>
> Thanks you! Please include GA Grid Architecture within the addon section..
>
> For example, Here is content from my initial post in Ignite users forum:
>
> http://apache-ignite-users.70518.x6.nabble.com/GA-Grid-
> Beta-Genetic-Algorithm-component-for-Ignite-is-here-td16041.html
>
> Best
> Turik
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/Ignite-Add-on-Extension-
> Request-Please-add-GA-Grid-beta-to-Ignite-website-tp20947p21042.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>

Re: Pentaho BI tool documentation for Ignite

[Prachi Garg]

Reviewed and made minor edits.

-Prachi

On Mon, Jul 31, 2017 at 1:58 PM, Denis Magda  wrote:

> Igniters,
>
> Slava Kopltilin contributed a new documentation that shows how to hook up
> Pentaho SQL tool with Ignite via the JDBC driver. Thanks, Slava!
> https://apacheignite-tools.readme.io/docs/pentaho
>
> Prachi, could you review the language and improve it whenever is needed?
>
> —
> Denis

Re: No direct way to download Ignite Web Agent

[Prachi Garg]

Hi Alexey,

That's great! I checked it on GridGain deployment, it looks good. However,
I don't see it on my local deployment. Was it not part of 2.0 release?

-Prachi

On Fri, May 19, 2017 at 2:21 AM, Alexey Kuznetsov <akuznet...@apache.org>
wrote:

> Prachi,
>
> We added "Download Web Agent" button on right top corner.
> Please, try it.
>
> On Thu, Apr 20, 2017 at 1:27 AM, Prachi Garg <pg...@gridgain.com> wrote:
>
>> Somewhere in the header would be more visible; I would prefer that.
>>
>> On Wed, Apr 19, 2017 at 12:37 AM, Alexey Kuznetsov <akuznet...@apache.org
>> >
>> wrote:
>>
>> > Prachi,
>> >
>> > I think we could add such link in "User" menu just after "Getting
>> started"
>> > item.
>> >
>> > Or, may be, as some icon on header?
>> >
>> > Vica, do you have any UI/UX suggestion for this?
>> >
>> > On Wed, Apr 19, 2017 at 12:46 PM, Dmitriy Setrakyan <
>> dsetrak...@apache.org
>> > >
>> > wrote:
>> >
>> > > Prachi, I completely agree. We should provide a way to download the
>> web
>> > > agent, along with installation instructions.
>> > >
>> > > Alexey K, can you comment?
>> > >
>> > > D.
>> > >
>> > > On Tue, Apr 18, 2017 at 4:16 PM, Prachi Garg <pg...@gridgain.com>
>> wrote:
>> > >
>> > > > Engineers,
>> > > >
>> > > > I realized that from the Web Console there is no direct way to
>> download
>> > > > Ignite Web Agent. The only way to download it is by going to either
>> > > Model,
>> > > > Monitoring, or Queries page (It's odd that to download the web
>> agent,
>> > you
>> > > > have to go to model -> import from db-> and then download when
>> > prompted).
>> > > > Since Ignite web agent is required for almost everything on the Web
>> > > > Console, shouldn't we have an option to download it from somewhere
>> in
>> > the
>> > > > top menu or side menu?
>> > > >
>> > > > -Prachi
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Alexey Kuznetsov
>> >
>>
>
>
>
> --
> Alexey Kuznetsov
>

Re: New version of Web Console released.

[Prachi Garg]

Tom, Denis

I can blog about Ignite Web Console's multi-cluster support.

-Prachi

On Fri, May 5, 2017 at 10:24 AM, Denis Magda  wrote:

> These is awesome news! Thanks Alex.
>
> Do you mind writing a blog post about the release sharing some thought on
> the multi-cluster support? [1]
> Is there anyone else who can take over this?
>
> [1] https://apacheignite-tools.readme.io/docs/multi-cluster-support
>
> —
> Denis
>
> On May 5, 2017, at 5:38 AM, Alexey Kuznetsov 
> wrote:
>
> Igniters!
>
> I'd like to announce that we just pushed new version of Ignite Web Console to
> master branch
>  and redeployed the new version on https://console.gridgain.com where you
> can give it a try right a way.
>
> NOTE 1: You will need to download new version of web-agent.
> NOTE 2: You may need to refresh page (F5 or Ctrl+R) in order to reload Web
>  Console.
>
> What's new:
>
>   * Multi-cluster support (see: https://apacheignite-tools.
> readme.io/docs/multi-cluster-support).
>   * Added support for "Kubernetes - IP finder" on Cluster Configuration
> screen.
>   * Improved import metadata from RDBMS - added support for table aliases.
>   * Many minor improvements and bugfixes.
>
> Stay tuned for updates!
>
> ---
> Alexey Kuznetsov
>
>
>

Re: "Apache Ignite University”

[Prachi Garg]

Great idea! +1

-P

On Thu, Apr 20, 2017 at 1:35 PM, Tom Diederich 
wrote:

> I’d also like to propose an enhancement to the community that I believe
> would be helpful to new and experienced Igniters alike: "Apache Ignite
> University.”
>
> It would be a new section of the Ignite website that features how-to’s in
> the form of blog posts, videos, even promoting "local" (wherever you might
> be) meetups and events. The goal is to help people from the very beginner
> to highly advanced with info and conversations.
>
> From "Getting started with Apache Ignite" all the way to the most advanced
> topics and tasks.
>
> What does everyone think? Yes or no?
>
> -Tom
>
>
>
>
>
>
>
>

Re: No direct way to download Ignite Web Agent

[Prachi Garg]

Somewhere in the header would be more visible; I would prefer that.

On Wed, Apr 19, 2017 at 12:37 AM, Alexey Kuznetsov <akuznet...@apache.org>
wrote:

> Prachi,
>
> I think we could add such link in "User" menu just after "Getting started"
> item.
>
> Or, may be, as some icon on header?
>
> Vica, do you have any UI/UX suggestion for this?
>
> On Wed, Apr 19, 2017 at 12:46 PM, Dmitriy Setrakyan <dsetrak...@apache.org
> >
> wrote:
>
> > Prachi, I completely agree. We should provide a way to download the web
> > agent, along with installation instructions.
> >
> > Alexey K, can you comment?
> >
> > D.
> >
> > On Tue, Apr 18, 2017 at 4:16 PM, Prachi Garg <pg...@gridgain.com> wrote:
> >
> > > Engineers,
> > >
> > > I realized that from the Web Console there is no direct way to download
> > > Ignite Web Agent. The only way to download it is by going to either
> > Model,
> > > Monitoring, or Queries page (It's odd that to download the web agent,
> you
> > > have to go to model -> import from db-> and then download when
> prompted).
> > > Since Ignite web agent is required for almost everything on the Web
> > > Console, shouldn't we have an option to download it from somewhere in
> the
> > > top menu or side menu?
> > >
> > > -Prachi
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
>

No direct way to download Ignite Web Agent

[Prachi Garg]

Engineers,

I realized that from the Web Console there is no direct way to download
Ignite Web Agent. The only way to download it is by going to either Model,
Monitoring, or Queries page (It's odd that to download the web agent, you
have to go to model -> import from db-> and then download when prompted).
Since Ignite web agent is required for almost everything on the Web
Console, shouldn't we have an option to download it from somewhere in the
top menu or side menu?

-Prachi

Re: Rights to Ignite wiki.

[Prachi Garg]

I've granted admin rights to Denis and editing rights to Ivan.

-Prachi

On Mon, Apr 10, 2017 at 12:18 PM, Konstantin Boudnik  wrote:

> Here's the list of the admins
>
> https://cwiki.apache.org/confluence/spaces/viewspacesummary.action?key=
> IGNITE=true
> --
>   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, Apr 10, 2017 at 12:17 PM, Denis Magda  wrote:
> > Thanks, Cos, I’m not an administrator either.
> >
> > Dmitriy, are you an admin? Can you grant me the admin rights as well?
> >
> > —
> > Denis
> >
> >> On Apr 10, 2017, at 12:14 PM, Konstantin Boudnik 
> wrote:
> >>
> >> One doesn't need to be committer to edit wiki - it is a separate
> resource IIRC.
> >> Now, to grand permissions to someone, an administrator needs to use
> >> "Space Tools" where permissions could be changed. I don't have admin
> >> privileges for Ignite wiki, so you need to do this yourself ;)
> >>
> >> 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, Apr 10, 2017 at 12:00 PM, Denis Magda 
> wrote:
> >>> This didn’t work for other contributors presented in JIRA’s special
> list.
> >>>
> >>> *Cos*, basing on your solid experience, is it true that only
> committers can edit wiki resources?
> >>>
> >>> Igor, I’ve added you to the contributors list in JIRA. Please try to
> edit the wiki page, probably you’re lucky one.
> >>>
> >>> —
> >>> Denis
> >>>
>  On Apr 10, 2017, at 11:54 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org> wrote:
> 
>  I think you just need to add a user in Jira.
> 
>  On Mon, Apr 10, 2017 at 11:53 AM, Denis Magda 
> wrote:
> 
> > Dmitriy S,
> >
> > How did you grant write permissions to Ignite wiki to contributor?
> See the
> > earlier messages from this discussion:
> >
> > http://apache-ignite-developers.2346864.n4.nabble.
> > com/Rights-to-Ignite-wiki-tp816p16387.html
> >
> >
> > I see no way how to do this for the migration guid. Only committers
> can
> > edit it.
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/
> > Apache+Ignite+2.0+Migration+Guide
> >
> >
> > —
> > Denis
> >
> > On Apr 10, 2017, at 10:52 AM, ivan.glukos 
> wrote:
> >
> > Hello,
> >
> > Can I get access to Ignite wiki as well?
> > I want to add some notes about per-page eviction to the 2.0
> migration guide
> > page:
> > https://cwiki.apache.org/confluence/display/IGNITE/
> > Apache+Ignite+2.0+Migration+Guide
> >
> > My login is ivan.glukos
> >
> > --
> > Best Regards,
> > Ivan Rakov
> >
> >
> >
> > --
> > View this message in context: http://apache-ignite-
> > developers.2346864.n4.nabble.com/Rights-to-Ignite-wiki-
> tp816p16387.html
> > Sent from the Apache Ignite Developers mailing list archive at
> Nabble.com.
> >
> >
> >
> >>>
> >
>

Fwd: Getting Started with Apache Ignite - Part 1

[Prachi Garg]

Posted the blog on DZone today; It should get published by Monday/Tuesday.

-P

-- Forwarded message --
From: Denis Magda 
Date: Tue, Mar 28, 2017 at 4:22 PM
Subject: Re: Getting Started with Apache Ignite - Part 1
To: dev@ignite.apache.org


Dani, excellent job!

*Prachi*, could you publish the article to DZone and update Ignite’s
blogging page? Since this will be a series of posts don’t add DZone version
of the article to Ignite’s page but rather add a link to the Dani’s own
blog right away.

*Dani*, to give more visibility to your work I would suggest registering
your blog on IMC Planned aggregator:
https://www.imcplanet.org 

—
Denis

> On Mar 28, 2017, at 11:42 AM, Dani Traphagen  wrote:
>
> Hi Igniters,
>
> I'm working on a multi-part series on working with Apache Ignite and just
> released my first post today.
> 
>
> This first post gives a conceptual basis to working with Ignite while
> follow up posts will work with code samples. Enjoy!
>
> Here's a direct link to the post: Getting Started to Apache Ignite - Part
1.
> 
>
> Cheers,
> Dani
> --
> Dani Traphagen | d...@gridgain.com
> Solutions Architect
> *GridGain*

Re: Making News page more visible

[Prachi Garg]

Sure, will implement it soon.

Thanks,
-P

On Wed, Mar 29, 2017 at 7:16 PM, Denis Magda  wrote:

> Prachi, as one of the site maintainers, would you mind contributing this?
>
> Denis
>
>
> On Wednesday, March 29, 2017, Tom Diederich 
> wrote:
>
>> Thanks, Denis! I agree that an anchor would make sense. Also really like
>> the
>> idea to add the social icons to make sharing fast and easy.
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-developer
>> s.2346864.n4.nabble.com/Making-News-page-more-visible-tp15763p15927.html
>> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>>
>

Re: [PMCs] Seeking your help for ASF's 18th Anniversary

[Prachi Garg]

Denis,

Please apply the attached patch.

-P

On Tue, Mar 28, 2017 at 9:34 AM, Denis Magda  wrote:

> Igniters,
>
> ASF needs you support. Please read below.
>
> Prachi, please add this logo to Ignite site’s footer and make it refer to
> the donation page [1]:
> https://blogs.apache.org/foundation/mediaresource/d67ca611-a57c-462d-ac23-
> 95063f81d175  d67ca611-a57c-462d-ac23-95063f81d175>
>
> [1] https://donate.apache.org 
>
> —
> Denis
>
> > Begin forwarded message:
> >
> > From: Sally Khudairi 
> > Subject: Re: [PMCs] Seeking your help for ASF's 18th Anniversary
> > Date: March 28, 2017 at 3:04:06 AM PDT
> > To: Sally Khudairi , ASF Fundraising <
> fundrais...@apache.org>
> > Reply-To: priv...@ignite.apache.org
> > Reply-To: Sally Khudairi 
> >
> > Hello everyone --thank you for your patience. We are now live:
> >
> >  - NASDAQ GlobeNewswire https://globenewswire.com/
> news-release/2017/03/28/945724/0/en/The-Apache-
> Software-Foundation-Announces-18-Years-of-Open-Source-Leadership.html
> >  - ASF "Foundation" blog https://s.apache.org/DHlr
> >  - @TheASF Twitter feed https://twitter.com/TheASF/
> status/846663405851291650
> >  - NEW! ASF LinkedIn page https://www.linkedin.com/
> company/the-apache-software-foundation
> >
> > ...as well as to annou...@apache.org and our dedicated media/analyst
> list. This will appear on the apache.org homepage later today.
> >
> > We encourage you to spread the word on your project pages and Twitter
> feeds, personal sites, as well as any employers/partners/* as appropriate.
> The relevant assets are:
> >
> >  - Support Apache logo https://blogs.apache.org/
> foundation/mediaresource/d67ca611-a57c-462d-ac23-95063f81d175
> >  - individual donations links https://donate.apache.org/ (immediate)
> and http://apache.org/foundation/contributing.html (will be updated later
> today)
> >
> > Thank you in advance for all your help and incredible support!
> >
> > Kind regards,
> > Sally
> >
> > = = = = =
> > vox +1 617 921 8656
> > gvox +1 646 598 4616
> > skype sallykhudairi
> >
> >
> > From: Sally Khudairi 
> > To: ASF Marketing & Publicity ; ASF Fundraising <
> fundrais...@apache.org>
> > Sent: Sunday, March 26, 2017 7:14 PM
> > Subject: Re: [PMCs] Seeking your help for ASF's 18th Anniversary
> >
> > Hello PMCs --a heads-up that our launch tomorrow has been postponed due
> to an outstanding issue with one of our payment processing systems.
> >
> > We are working on the issue and are hoping to announce at 6AM ET on
> Tuesday 28 March. Fingers crossed.
> >
> > I'll confirm once we're live. We appreciate your patience!
> >
> > Kind thanks,
> > Sally
> >
> > = = = = =
> > vox +1 617 921 8656
> > gvox +1 646 598 4616
> > skype sallykhudairi
> >
> >
> > From: Sally Khudairi 
> > To: ASF Marketing & Publicity ; Apache Software
> Foundation 
> > Sent: Friday, March 24, 2017 4:10 PM
> > Subject: [PMCs] Seeking your help for ASF's 18th Anniversary
> >
> > Hello Apache PMCs (in blindcopy) --I trust you are well.
> >
> > I wanted to give you a heads-up that at 6AM ET this Monday, 27 March, we
> will be issuing a press release announcing the ASF's 18th Anniversary. This
> will be posted across the ASF's usual communication channels (
> blogs.apache.org, annou...@apache.org ,
> @TheASF Twitter feed, and ASF LinkedIn page).
> >
> > Many of the achievements highlighted in the press release are a direct
> result of your efforts :-)
> >
> > Coupled with this announcement is our interest in boosting ASF
> fundraising efforts in the form of individual donations. We will be
> launching our new "Support Apache" campaign, and are inviting folks to make
> a donation of any size (if possible) as a one-time donation or on a
> recurring basis.
> >
> > To that end, we are asking all PMCs to add the Support Apache logo
> https://s.apache.org/SupportApache  to
> your project pages with a link to the campaign when we go live next week. I
> will confirm the link when we're live.
> >
> > Thank you in advance for helping spread the word to your communities.
> Also, if there are any organizations involved with your projects that may
> be interested in ASF Sponsorship, we'd love to hear about it.
> >
> > We appreciate all your support in helping us continue to build for our
> future.
> >
> > Kindest regards,
> > Sally
> >
> >
> > = = = = =
> > vox +1 617 921 8656
> > gvox +1 646 598 4616
> > skype sallykhudairi
> >
> >
> >
> >
>
>

Re: Making News page more visible

[Prachi Garg]

Agree with both the suggestions. I have attached the patch for the header.
Lmk if I should add the social media links on the news page.

-P

On Fri, Mar 24, 2017 at 11:53 AM, Denis Magda  wrote:

> Igniters, especially Prachi, Mauricio, Dmitriy,
>
> The news section [1] of the site was evolved significantly over the past
> time.
>
> First, I suggest us making it more visible by adding a link to it in the
> top-most header placing between “blogs” and “twitter”.
>
> Second, can we anchor every piece of news [1] so that it can be referred
> directly from other sources. Also it makes sense to add “Twitter”, “FB”,
> “LinkedIn” icons close to every news so that we can promote them easily.
>
> What do you think?
>
> [1] https://ignite.apache.org/news.html
>
> —
> Denis
>

Web Console Monitoring - Running queries page text

[Prachi Garg]

Please fix the text for Running queries page (shown when there is no
information available)-

"Query monitoring is not available for the current cluster. This may be
because either no query has been executed or queries' duration is less then
the specified in filter."

Thanks,
-Prachi

Incorrect link on LinkedIn page

[Prachi Garg]

Igniters,

The LinkedIn page for Ignite[1] still points to the incubator link[2]. Can
someone (whoever owns the account) please fix it?

[1] https://www.linkedin.com/company/apache-ignite
[2] http://ignite.incubator.apache.org/

-Prachi

Re: Issues with local deployment of the Web Console

[Prachi Garg]

Looks like I can't attach images to dev list. I have uploded the images
here -
https://drive.google.com/drive/folders/0B13J0oQz4pZxZThkUlJfMWJhTGM?usp=sharing

On Wed, Feb 1, 2017 at 3:11 PM, Prachi Garg <pg...@gridgain.com> wrote:

> Engineers,
>
> I deployed the Web Console locally, and found a couple of issues while
> trying to add and save a cluster on http://localhost:9000/configur
> ation/clusters page-
>
>1. There is no Java/XML code, on the right side.
>2. No list of cluster names.
>3. No 'undo' arrow/icon on the red button next to 'Save'
>4. No green notification, on top right of the screen, for successfully
>saving a cluster
>5. I keep getting the notification/warning popup box for unsaved
>changes although the log shows that a cluster is saved.
>6. I have to manually refresh the page to see some of the updates.
>7. I see some, not all, of the above mentioned issues when trying to
>add and save a cache.
>8. There is no Java or XML code on the Summary page.
>
> Please see the attached images and the log below:
>
> POST /configuration/clusters/save 400 13.376 ms - 44
>
> POST /configuration/clusters/save 400 11.070 ms - 44
>
> POST /configuration/clusters/save 400 10.033 ms - 44
>
> POST /configuration/caches/save 400 8.311 ms - 41
>
> POST /configuration/caches/save 400 7.587 ms - 41
>
>
> I followed this documentation for local deployment -
> https://apacheignite.readme.io/docs/local-deployment.
>
> Thanks,
>
> -Prachi
>
>
>

Issues with local deployment of the Web Console

[Prachi Garg]

Engineers,

I deployed the Web Console locally, and found a couple of issues while
trying to add and save a cluster on http://localhost:9000/
configuration/clusters page-

   1. There is no Java/XML code, on the right side.
   2. No list of cluster names.
   3. No 'undo' arrow/icon on the red button next to 'Save'
   4. No green notification, on top right of the screen, for successfully
   saving a cluster
   5. I keep getting the notification/warning popup box for unsaved changes
   although the log shows that a cluster is saved.
   6. I have to manually refresh the page to see some of the updates.
   7. I see some, not all, of the above mentioned issues when trying to add
   and save a cache.
   8. There is no Java or XML code on the Summary page.

Please see the attached images and the log below:

POST /configuration/clusters/save 400 13.376 ms - 44

POST /configuration/clusters/save 400 11.070 ms - 44

POST /configuration/clusters/save 400 10.033 ms - 44

POST /configuration/caches/save 400 8.311 ms - 41

POST /configuration/caches/save 400 7.587 ms - 41


I followed this documentation for local deployment -
https://apacheignite.readme.io/docs/local-deployment.

Thanks,

-Prachi

Re: Apache Ignite SEO Audit

[Prachi Garg]

Dmitriy,

I don't have admin rights; you do. You can follow the instructions here -
https://support.google.com/webmasters/answer/2453966

-Prachi

On Mon, Jan 23, 2017 at 3:45 PM, Dmitriy Setrakyan 
wrote:

> Prachi, would you be the one to help Mauricio here?
>
> On Mon, Jan 23, 2017 at 3:23 PM, Mauricio Stekl 
> wrote:
>
> > No, I’m afraid I can’t use the same file. However it seems there was
> > already a GWT account setup for this domain then. So I could be granted
> > access to that account instead. Would that be possible?
> >
> > Thanks.
> > Mauricio
> >
> >
> > > On Jan 23, 2017, at 18:24, Dmitriy Setrakyan 
> > wrote:
> > >
> > > Mauricio, we already have similar file added for google site
> > verification:
> > > google9276fe2a42313afd.html
> > >
> > > Can you reuse this one?
> > >
> > > D.
> > >
> > > On Mon, Jan 23, 2017 at 12:20 PM, Mauricio Stekl <
> mauri...@gridgain.com>
> > > wrote:
> > >
> > >> Hi,
> > >> In order to setup the Google Webmaster Tools account on
> > ignite.apache.org,
> > >> I would need to upload the attached .html file to the root of the
> > website.
> > >>
> > >> Could someone with commit privileges help me with this?
> > >>
> > >> Thanks in advance.
> > >>
> > >> Mauricio
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Jan 19, 2017, at 19:29, Dmitriy Setrakyan 
> > >> wrote:
> > >>
> > >> Hi Terry, this should not be a problem. I have sent you the
> credentials
> > >> privately. Let me know if you need more help.
> > >>
> > >> D.
> > >>
> > >> On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman <
> teris...@gridgain.com>
> > >> wrote:
> > >>
> > >> Hi All,
> > >>
> > >>
> > >>
> > >> In order to proceed effectively with the SEO audit of the Apache
> Ignite
> > >> website, we need admin access to the Google Analytics account for the
> > >> website. Once we have the Google Analytics account access, we will
> setup
> > >> Google Webmaster Tools for the website (it isn't setup currently)
> which
> > >> will
> > >> give us insights into a variety of characteristics of the website.
> > >>
> > >>
> > >>
> > >> If anyone has any concerns about this, please let me know. I look
> > forward
> > >> to
> > >> getting started on this audit.
> > >>
> > >>
> > >>
> > >> Thanks,
> > >>
> > >>
> > >>
> > >> Terry
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> >
> >
>

Re: Hibernate OGM for Ignite. I need a help with documentation

[Prachi Garg]

Hi Victor,

I have tried to fix the document. However, I do have some questions. Please
see my comments in the document.

https://docs.google.com/document/d/1ZSFt9NPnN8EyOpNnNguc5-9FIDr4RfQLfAZMH0VgBPc/edit#

Thanks,
-Prachi

On Tue, Jan 17, 2017 at 7:22 PM, Denis Magda  wrote:

> Hi Victor,
>
> This seems to be a duplicate message. Please join the conversation in the
> original message
> http://apache-ignite-developers.2346864.n4.nabble.
> com/Hibernate-OGM-for-Ignite-I-need-a-help-with-documentation-tp13762.html
>  com/Hibernate-OGM-for-Ignite-I-need-a-help-with-documentation-tp13762.html
> >
>
> —
> Denis
>
> > On Jan 17, 2017, at 12:12 PM, Victor Z  wrote:
> >
> > Hi everybody!
> >
> > Hibernate OGM  is a JPA implementation for
> NoSQL
> > datastores. I'm creating module for Apache Ignite.
> > Here is my work
> > ,
> and pull
> > request  ApacheIgnite>
> > to Hibernate OGM
> > I've almost done, but there is one issue with documentation. I have to
> > write it.
> > But I'm programmer, not a techwriter, and my English is not very good.
> > I made a draft of documentation
> > https://drive.google.com/open?id=0B2da3AGK_cO6TWpvVzFrWWF0dEk
> >
> > Could you please take a look at this to correct mistakes or to add some
> > useful information?
> >
> > Here is existing documentation
> >  that I
> > used as an example.
> >
> > Thank you in advance,
> > Victor
>
>

Ignite Web Console Monitoring Video on YouTube

[Prachi Garg]

Hello Igniters,

Check out the latest Ignite Web Console video on YouTube -
http://youtu.be/H8cwYSJATto

This video shows how to use Ignite Web Console Monitoring in Demo mode.

-Prachi

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Prachi Garg]

Roman's blog has been added to the website - https://ignite.apache.org/
blogs.html

-Prachi




On Mon, Jan 9, 2017 at 10:33 AM, Denis Magda  wrote:

> Roman, perfect! Well done!
>
> *Prachi*, please add Roman’s blog to Apache Ignite’s blogs list:
> https://ignite.apache.org/blogs.html
>
> *Sally*, considering that all the information is already at place is it a
> good time to wrap it up in an Apache official announcement?
>
> —
> Denis
>
> On Jan 9, 2017, at 1:43 AM, Roman Shtykh  wrote:
>
> Denis, I published a short article on https://dzone.com/articles/
> handling-apache-ignite-cluster-data-via-redis-prot
>
> -Roman
>
>
> On Saturday, December 31, 2016 12:50 AM, Denis Magda 
> wrote:
>
>
> Roman, amazing thanks!
>
> You can use any blogging engine you like. After the blog post is ready
> notify the community and Prachi will send your material to dzone.com and
> when it’s accepted there we will public it on Ignite’s blogging page (
> https://ignite.apache.org/blogs.html).
>
> As for the format, I would suggest making a quick walk-through guidance
> including code snippets and showing how to connect to the cluster from
> Python or Ruby (whatever you like most) and work with it. You can do
> something like I did for PHP
> https://dzone.com/articles/apache-ignite-enables-full-
> fledged-sql-support-for
>
> —
> Denis
>
> On Dec 30, 2016, at 4:09 AM, Roman Shtykh 
> wrote:
>
> Sure, Denis, I can write about Redis protocol support. Can you please
> instruct me about the format and how/where to submit?
> Roman
>
>
>On Friday, December 30, 2016 8:11 AM, Sally Khudairi 
> wrote:
>
>
> Boop! Sorry about that...indeed, I wrote Roman's name in my notes next to
> "1.8 release manager?" and clearly combined the two.
> Apologies for alarming you.
> But that is a good hint, Denis 
> Cheers,Sally
>
>
> [From the mobile; please excuse top-posting, spelling/spacing errors, and
> brevity]
>
>
>
>
>   On Thu, Dec 29, 2016 at 17:58, Denis Magda wrote:
> Sally, looks like you got confused with this
>
> On Dec 29, 2016, at 2:38 PM, Sally Khudairi  wrote:
> And thanks in advance, Roman Shtykh, for acting as project spokesperson in
> your role as release manager. Participation from the community at-large is
> greatly appreciated!
>
> Roman have never been a release manager yet. However, this is just a
> matter of time and his interest/intention ;)
> —Denis
>
>
>
>
>
>

Re: DML Documentation Readiness

[Prachi Garg]

Sure, will look into it.

-P

On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda  wrote:

> I’ve finished the review and released all the parts of DML documentation
> [1].
>
> Prachi, could you review whole SQL Grid documentation [2] including [1]?
> Also it will be great if you check this newly added section [3].
>
> [1] http://apacheignite.gridgain.org/docs/dml
> [2] http://apacheignite.gridgain.org/docs/sql-grid
> [3] http://apacheignite.gridgain.org/docs/binary-
> marshaller#handling-hash-code-generation-and-equals-execution
>
> —
> Denis
>
> On Dec 9, 2016, at 12:34 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
> Denis,
>
> About your question: 'putIfAbsent' is used only when we have single
> key-value pair to process as long as we don't have method like 'put
> all if absent'. When there's a bunch of pairs, an entry processor is
> created for each pair to make its processing atomic (effectively CAS
> style processing), and all those processors are then executed via
> 'invokeAll'.
>
> - Alex
>
> 2016-12-09 8:17 GMT+03:00 Denis Magda :
>
> Alexander, thanks for all the material you’ve prepared so far.
>
> Actually, I’ve reviewed, restructured and released only a part of it [1].
>
> The rest, that is missing, requires more time from my side and I’ll be
> releasing additional blocks throughout the next week. The full
> documentation
> with the unreviewed parts is invisible and located here [2].
>
> Please don’t modify neither of the docs ([1] and [2]) until I’ve finished
> with the overall review. Send all your suggestions over the email.
>
> At the moment I have the following question. What cache method(s) do we
> convert INSERT statements to [3]? Is it ‘putIfAbsent’?
>
> [1] https://apacheignite.readme.io/docs/dml
> [2] https://apacheignite.readme.io/docs/distributed-dml-to-be-reviewe
> [3] https://apacheignite.readme.io/docs/dml#section-insert
>
> —
> Denis
>
> On Dec 8, 2016, at 1:35 AM, Alexander Paschenko
>  wrote:
>
> Denis,
>
> it's all ready, JDBC driver page is also updated (I've created a
> hidden clone page, please find it on the left) as well as one on
> binary marshaller. Also I've renamed 'distributed DML' page to just
> 'DML' as long as there's much less to distribution of DML operations
> themselves than to queries and there's clearly no need to make another
> doc page to distinguish. Removed batches mention from limitations.
>
> - Alex
>
> 2016-12-08 5:26 GMT+03:00 Denis Magda :
>
> Alexander,
>
> How close are you to the finalization of the DML doc?
> https://apacheignite.readme.io/docs/distributed-dml
>
> Since we’re approaching 1.8 release I would like to do a final review of it
> polishing whatever is needed tomorrow.
>
> As I see that only the limitations section is left. The first note is that
> I
> wouldn’t mention “JDBC Batching mode” for now because this is something
> that
> doesn’t affect the usability and SQL API's scope of support.
>
> —
> Denis
>
>
>

Re: Hibernate OGM and Ignite (beginning of the story)

[Prachi Garg]

Shamim,

Your blog has been added to the Ignite blog list-
https://ignite.apache.org/blogs.html

-Prachi

On Tue, Dec 13, 2016 at 4:35 PM, Denis Magda  wrote:

> Shamim, great thanks!
>
> Copying our conversion to Ignite’s dev and user lists.
>
> Igniters, Shamim posted a useful blog post about the usage of Hibernate
> OGM and Ignite integration.
> https://dzone.com/articles/apache-ignite-with-jpa-a-missing-element <
> https://dzone.com/articles/apache-ignite-with-jpa-a-missing-element>
>
> I hope this integration will be merged soon into Hibernate repository but
> you already can give it a try in practice.
>
> Prachi, could you add this blog post to our blogs list? Shamim, if you
> don’t mind we will use this picture of you.
> https://dzone.com/users/284671/shamim_ru.html  284671/shamim_ru.html>
>
>
> —
> Denis
>
> > On Dec 13, 2016, at 2:54 AM, sre...@yandex.ru wrote:
> >
> > Denis, thank's for your interest to add this article to Apache Ignite
> blog. Yes, you can add this it to Ignite blog (actually, i do not know,
> where to add it properly).
> >
> > Best regards
> >
> >  Shamim Ahmed
> >
> > _
> > Sent from http://apache-ignite-users.70518.x6.nabble.com
> >
>
>

Re: Off-Heap SQL Indexes

[Prachi Garg]

Fixed. Please review -
http://apacheignite.gridgain.org/v1.7/docs/sql-queries#off-heap-sql-indexes

-P

On Mon, Nov 7, 2016 at 9:36 AM, Denis Magda <dma...@gridgain.com> wrote:

> Sergi,
>
> May be you use
> some weird email client which renders >> signs wrong?
>
>
> Right, my Apple’s Mail agent omitted ‘>’ character from your original
> statement applying some HTML formatting.
>
> *Prachi*, please update all the docs keeping in my that this sentence is
> technically correct
>
> SQL engine will store indexes in the off-heap region if
> setOffHeapMaxMemory parameter >= 0 or setMemoryMode is set to any supported
> off-heap mode. It worth to mention that setOffHeapMaxMemory is set to 0
> automatically if it’s value is less than -1 and one of off-heap memory
> modes is used.
>
>
> —
> Denis
>
> On Nov 5, 2016, at 6:23 AM, Sergi Vladykin <sergi.vlady...@gmail.com>
> wrote:
>
> Your final statement seems correct to me, but I said exactly that, I don't
> know where did you get that setOffHeapMaxMemory must be 0. May be you use
> some weird email client which renders >> signs wrong?
>
> Sergi
>
> 2016-11-04 22:25 GMT+03:00 Denis Magda <dma...@gridgain.com>:
>
> Sergi,
>
> Thanks, now I found the exact conditions that switch the indexes from
> on-heap to off-heap.
>
> But looks like you did a misprint in your conclusion saying that
> setOffHeapMaxMemory should be 0.
>
> Thus from the user standpoint we can say, that if either
>
> setOffHeapMaxMemory
>
> = 0 or setMemoryMode is set to any of off-heap modes, then indexes will
>
> go
>
> off-heap.
>
>
> In fact, as you elaborated earlier, it has to be >= 0 which leads to the
> following final statement:
>
> SQL engine will store indexes in the off-heap region if
> setOffHeapMaxMemory parameter >= 0 or setMemoryMode is set to any supported
> off-heap mode. It worth to mention that setOffHeapMaxMemory is set to 0
> automatically if it’s value is less than -1 and one of off-heap memory
> modes is used.
>
> Are we on the same page now?
>
> —
> Denis
>
> On Nov 4, 2016, at 1:51 AM, Sergi Vladykin <sergi.vlady...@gmail.com>
>
> wrote:
>
>
> Denis,
>
> I checked the code now as well. I actually was wrong, but your statement
>
> is
>
> wrong either.
>
> If we are talking about indexes then the exact condition when index will
>
> be
>
> off-heap is the following: either setOffHeapMaxMemory >= 0 or
>
> setMemoryMode
>
> is OFFHEAP_TIERED.
>
> But if setMemoryMode is set to one of off-heap modes and
>
> setOffHeapMaxMemory is
>
> -1, then setOffHeapMaxMemory is silently getting switched to 0.
>
> Thus from the user standpoint we can say, that if either
>
> setOffHeapMaxMemory
>
> = 0 or setMemoryMode is set to any of off-heap modes, then indexes will
>
> go
>
> off-heap.
>
> Sergi
>
> 2016-11-04 6:30 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>:
>
> Do we currently throw an exception if memory mode is set to off-heap by
>
> the
>
> max-offheap-memory is set to "-1"? Otherwise, it can get very confusing
>
> to
>
> users.
>
> On Thu, Nov 3, 2016 at 10:22 AM, Denis Magda <dma...@gridgain.com>
>
> wrote:
>
>
> Sergi,
>
> Referring to your response and the source code I should say that, in
>
> fact,
>
> the documentation has to state the following:
>
> “To place both data and indexes in off heap memory CacheConfiguration.
>
> setMemoryMode
>
> has to be set to one of off heap modes and CacheConfiguration.
>
> setOffHeapMaxMemory
>
> has to be set to a value different from -1 (disabled). If at least one
>
> of
>
> these conditions is not met then both data and indexes will be located
>
> in
>
> on heap memory”
>
> Is this statement correct?
>
> —
> Denis
>
> On Nov 3, 2016, at 2:53 AM, Sergi Vladykin <sergi.vlady...@gmail.com>
>
> wrote:
>
>
> Prachi,
>
> In [2] we refer to the same CacheConfiguration.setOffHeapMaxMemory
> property, so [1] is correct. If setOffHeapMaxMemory is disabled (set
>
> to
>
> -1), then indexes will never be stored offheap, regardless of
>
> setMemoryMode
>
> setting.
>
> Probably we have to change [2] to make it clear, that it is about
> setOffHeapMaxMemory
> but not about setMemoryMode.
>
> Sergi
>
>
> 2016-11-03 2:25 GMT+03:00 Prachi Garg <pg...@gridgain.com>:
>
> Engineers,
>
> I was going through documentation for Off-Heap SQL Indexes
> <https://apacheignite.readme.io/docs/sql-queries#off-heap-
>
> s

Off-Heap SQL Indexes

[Prachi Garg]

Engineers,

I was going through documentation for Off-Heap SQL Indexes
 and
found two contradicting statements-

According to [1] -  " `CacheConfiguration.setOffHeapMaxMemory` is the only
property to enable or disable off-heap indexing. While
CacheConfiguration.setMemoryMode is used to configure off-heap memory
, it does not
have any effect on indexing."

According to [2] -  "Note that when off-heap memory is configured, Ignite
will store query indexes off-heap as well."


Which one is true?

[1] - https://apacheignite.readme.io/docs/sql-queries#off-heap-sql-indexes

[2] - http://apacheignite.gridgain.org/docs/off-heap-memory


Thanks,

-Prachi

New page on the website!

[Prachi Garg]

Hello Igniters,

Check out the new page on the Ignite website -
https://ignite.apache.org/features/rdbmsintegration.html to learn how
Ignite can seamlessly integrate with underlying data stores, and
automatically generate domain model POJOs as well as XML and Java
configurations.

-Prachi

Re: Maintaining documentation consistency on readme.io

[Prachi Garg]

Changes to the existing pages will still have to be copied manually; but
since we are not maintaining two versions (current and future) at the same
time, it may be a lesser overhead. Once a new version is released, we
hardly go back to the previous versions to fix anything.

-P

On Wed, Aug 24, 2016 at 9:42 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Prarchi, great idea. We should follow it.
>
> However, this addresses only new content. What about changes to the
> existing pages?
>
> D.
>
> On Wed, Aug 24, 2016 at 5:15 PM, Denis Magda <dma...@gridgain.com> wrote:
>
> > Prachi,
> >
> > This is an excellent idea!
> >
> > Would you mind adding a new page to this [1] section?
> >
> > After the page is ready we also need to leave a reference to it under
> this
> > [2] section.
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> Development+Process
> > <https://cwiki.apache.org/confluence/display/IGNITE/Development+Process>
> > [2] https://cwiki.apache.org/confluence/display/IGNITE/How+
> > to+Contribute#HowtoContribute-Documentation <
> > https://cwiki.apache.org/confluence/display/IGNITE/How+
> > to+Contribute#HowtoContribute-Documentation>
> >
> > —
> > Denis
> >
> > > On Aug 24, 2016, at 10:58 AM, Prachi Garg <pg...@gridgain.com> wrote:
> > >
> > > Igniters,
> > >
> > > Since readme.io does not automatically copy the changes from the
> current
> > > version to the subsequent version, I have the following suggestion:
> > >
> > > Create the document for future releases within the document for the
> > current
> > > version, and keep the pages hidden. After the new release, create the
> new
> > > version for the document and unhide the pages.
> > >
> > > This way we don't have to manually copy the document between the two
> > > versions.
> > >
> > > Thoughts?
> > >
> > > -Prachi
> >
> >
>

Maintaining documentation consistency on readme.io

[Prachi Garg]

Igniters,

Since readme.io does not automatically copy the changes from the current
version to the subsequent version, I have the following suggestion:

Create the document for future releases within the document for the current
version, and keep the pages hidden. After the new release, create the new
version for the document and unhide the pages.

This way we don't have to manually copy the document between the two
versions.

Thoughts?

-Prachi

Documentation for AOP-based Grid Enabling

[Prachi Garg]

Engineers,

I have added documentation for AOP-based Grid Enabling -
http://apacheignite.gridgain.org/docs/aop-based-grid-enabling.

Can someone please review?

-P