You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Alexey Kuznetsov <ak...@apache.org> on 2017/06/05 14:54:15 UTC
New version of Web Console released
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 GridGain infrastructure (https://console
.gridgain.com) where you can give it a try right a way.
NOTE: You may need to refresh page (F5 or Ctrl+R) in order to reload Web
Console.
*What's new:*
* Support for Ignite 1.x / Ignite 2.0
You can configure, query and monitoring Ignite 1.x and Ignite 2.0 from
single Web Console.
* Improved build with web pack
*Coming soon:*
* Notifications about Web Console updates!
Web console will show banner with warning about upcoming updates.
* Support for Ignite 2.1
* Improved stack trace for SQL errors.
Stay tuned for updates!
--
Alexey Kuznetsov
Re: New version of Web Console released
Posted by Muthu <mu...@gmail.com>.
Sure i will do that..thanks!
Regards,
Muthu
On Wed, Jun 7, 2017 at 5:06 AM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> Muthu,
>
> It is better to start separate thread on user list about your use case.
>
> On Wed, Jun 7, 2017 at 4:22 PM, Muthu <mu...@gmail.com> wrote:
>
>>
>> Thanks Alexey! for the pointers. For the ORM alternate case the use case
>> is the below (basically today we are thinking of using Ignite with MyBatis
>> with Ignite being the L2 cache (among other things) & MyBatis being the
>> persistence framework, the question is can Ignite do the cache with the Web
>> console's RDBMS Integration or Model support being used to play the role
>> of the persistence framework so it will be an all Ignite thingy),
>>
>> 1. A way to write DTOs to ignite cache which will then automatically
>> (async aswell) persist to DB (model/DTO generation, db persistence, etc)
>> -- This includes insert, update & delete and batch/bulk operations
>>
>> 2. A way to read from ignite cache which will automatically read from DB
>> if not in cache
>> -- This includes read based on any predicate (where clause), custom
>> select sql queries, bulk operations
>>
>> Regards,
>> Muthu
>>
>> On Wed, Jun 7, 2017 at 12:19 AM, Alexey Kuznetsov <ak...@apache.org>
>> wrote:
>>
>>> Muthu,
>>>
>>> >> Is the web console not part of or deploy-able from the ignite fabric
>>> distrib
>>> Yes. It is not part of binary distribution.
>>> You can build it from sources or use Docker image (see:
>>> https://hub.docker.com/r/apacheignite/web-console-standalone/tags/)
>>>
>>> >> .but i do not find any directory named "modules" under my IGNITE_HOME
>>> You need to download SOURCE release.
>>>
>>>
>>> >>> Can i download only a trial version from console.gridgain.com ?
>>> No. console.gridgain.com contains Web Console that based on Apache
>>> Ignite code base, but with additional features developed by GridGain.
>>> Please contact GridGain for that.
>>>
>>> >> Will i able to use this as an alternative to say an ORM like MyBatis?
>>> It depends in what you need. Please describe your use case.
>>>
>>>
>>>
>>> --
>>> Alexey Kuznetsov
>>>
>>
>>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: New version of Web Console released
Posted by Muthu <mu...@gmail.com>.
Sure i will do that..thanks!
Regards,
Muthu
On Wed, Jun 7, 2017 at 5:06 AM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> Muthu,
>
> It is better to start separate thread on user list about your use case.
>
> On Wed, Jun 7, 2017 at 4:22 PM, Muthu <mu...@gmail.com> wrote:
>
>>
>> Thanks Alexey! for the pointers. For the ORM alternate case the use case
>> is the below (basically today we are thinking of using Ignite with MyBatis
>> with Ignite being the L2 cache (among other things) & MyBatis being the
>> persistence framework, the question is can Ignite do the cache with the Web
>> console's RDBMS Integration or Model support being used to play the role
>> of the persistence framework so it will be an all Ignite thingy),
>>
>> 1. A way to write DTOs to ignite cache which will then automatically
>> (async aswell) persist to DB (model/DTO generation, db persistence, etc)
>> -- This includes insert, update & delete and batch/bulk operations
>>
>> 2. A way to read from ignite cache which will automatically read from DB
>> if not in cache
>> -- This includes read based on any predicate (where clause), custom
>> select sql queries, bulk operations
>>
>> Regards,
>> Muthu
>>
>> On Wed, Jun 7, 2017 at 12:19 AM, Alexey Kuznetsov <ak...@apache.org>
>> wrote:
>>
>>> Muthu,
>>>
>>> >> Is the web console not part of or deploy-able from the ignite fabric
>>> distrib
>>> Yes. It is not part of binary distribution.
>>> You can build it from sources or use Docker image (see:
>>> https://hub.docker.com/r/apacheignite/web-console-standalone/tags/)
>>>
>>> >> .but i do not find any directory named "modules" under my IGNITE_HOME
>>> You need to download SOURCE release.
>>>
>>>
>>> >>> Can i download only a trial version from console.gridgain.com ?
>>> No. console.gridgain.com contains Web Console that based on Apache
>>> Ignite code base, but with additional features developed by GridGain.
>>> Please contact GridGain for that.
>>>
>>> >> Will i able to use this as an alternative to say an ORM like MyBatis?
>>> It depends in what you need. Please describe your use case.
>>>
>>>
>>>
>>> --
>>> Alexey Kuznetsov
>>>
>>
>>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: New version of Web Console released
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
Muthu,
It is better to start separate thread on user list about your use case.
On Wed, Jun 7, 2017 at 4:22 PM, Muthu <mu...@gmail.com> wrote:
>
> Thanks Alexey! for the pointers. For the ORM alternate case the use case
> is the below (basically today we are thinking of using Ignite with MyBatis
> with Ignite being the L2 cache (among other things) & MyBatis being the
> persistence framework, the question is can Ignite do the cache with the Web
> console's RDBMS Integration or Model support being used to play the role
> of the persistence framework so it will be an all Ignite thingy),
>
> 1. A way to write DTOs to ignite cache which will then automatically
> (async aswell) persist to DB (model/DTO generation, db persistence, etc)
> -- This includes insert, update & delete and batch/bulk operations
>
> 2. A way to read from ignite cache which will automatically read from DB
> if not in cache
> -- This includes read based on any predicate (where clause), custom
> select sql queries, bulk operations
>
> Regards,
> Muthu
>
> On Wed, Jun 7, 2017 at 12:19 AM, Alexey Kuznetsov <ak...@apache.org>
> wrote:
>
>> Muthu,
>>
>> >> Is the web console not part of or deploy-able from the ignite fabric
>> distrib
>> Yes. It is not part of binary distribution.
>> You can build it from sources or use Docker image (see:
>> https://hub.docker.com/r/apacheignite/web-console-standalone/tags/)
>>
>> >> .but i do not find any directory named "modules" under my IGNITE_HOME
>> You need to download SOURCE release.
>>
>>
>> >>> Can i download only a trial version from console.gridgain.com ?
>> No. console.gridgain.com contains Web Console that based on Apache
>> Ignite code base, but with additional features developed by GridGain.
>> Please contact GridGain for that.
>>
>> >> Will i able to use this as an alternative to say an ORM like MyBatis?
>> It depends in what you need. Please describe your use case.
>>
>>
>>
>> --
>> Alexey Kuznetsov
>>
>
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: New version of Web Console released
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
Muthu,
It is better to start separate thread on user list about your use case.
On Wed, Jun 7, 2017 at 4:22 PM, Muthu <mu...@gmail.com> wrote:
>
> Thanks Alexey! for the pointers. For the ORM alternate case the use case
> is the below (basically today we are thinking of using Ignite with MyBatis
> with Ignite being the L2 cache (among other things) & MyBatis being the
> persistence framework, the question is can Ignite do the cache with the Web
> console's RDBMS Integration or Model support being used to play the role
> of the persistence framework so it will be an all Ignite thingy),
>
> 1. A way to write DTOs to ignite cache which will then automatically
> (async aswell) persist to DB (model/DTO generation, db persistence, etc)
> -- This includes insert, update & delete and batch/bulk operations
>
> 2. A way to read from ignite cache which will automatically read from DB
> if not in cache
> -- This includes read based on any predicate (where clause), custom
> select sql queries, bulk operations
>
> Regards,
> Muthu
>
> On Wed, Jun 7, 2017 at 12:19 AM, Alexey Kuznetsov <ak...@apache.org>
> wrote:
>
>> Muthu,
>>
>> >> Is the web console not part of or deploy-able from the ignite fabric
>> distrib
>> Yes. It is not part of binary distribution.
>> You can build it from sources or use Docker image (see:
>> https://hub.docker.com/r/apacheignite/web-console-standalone/tags/)
>>
>> >> .but i do not find any directory named "modules" under my IGNITE_HOME
>> You need to download SOURCE release.
>>
>>
>> >>> Can i download only a trial version from console.gridgain.com ?
>> No. console.gridgain.com contains Web Console that based on Apache
>> Ignite code base, but with additional features developed by GridGain.
>> Please contact GridGain for that.
>>
>> >> Will i able to use this as an alternative to say an ORM like MyBatis?
>> It depends in what you need. Please describe your use case.
>>
>>
>>
>> --
>> Alexey Kuznetsov
>>
>
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: New version of Web Console released
Posted by Muthu <mu...@gmail.com>.
Thanks Alexey! for the pointers. For the ORM alternate case the use case is
the below (basically today we are thinking of using Ignite with MyBatis
with Ignite being the L2 cache (among other things) & MyBatis being the
persistence framework, the question is can Ignite do the cache with the Web
console's RDBMS Integration or Model support being used to play the role of
the persistence framework so it will be an all Ignite thingy),
1. A way to write DTOs to ignite cache which will then automatically (async
aswell) persist to DB (model/DTO generation, db persistence, etc)
-- This includes insert, update & delete and batch/bulk operations
2. A way to read from ignite cache which will automatically read from DB if
not in cache
-- This includes read based on any predicate (where clause), custom
select sql queries, bulk operations
Regards,
Muthu
On Wed, Jun 7, 2017 at 12:19 AM, Alexey Kuznetsov <ak...@apache.org>
wrote:
> Muthu,
>
> >> Is the web console not part of or deploy-able from the ignite fabric
> distrib
> Yes. It is not part of binary distribution.
> You can build it from sources or use Docker image (see:
> https://hub.docker.com/r/apacheignite/web-console-standalone/tags/)
>
> >> .but i do not find any directory named "modules" under my IGNITE_HOME
> You need to download SOURCE release.
>
>
> >>> Can i download only a trial version from console.gridgain.com ?
> No. console.gridgain.com contains Web Console that based on Apache Ignite
> code base, but with additional features developed by GridGain.
> Please contact GridGain for that.
>
> >> Will i able to use this as an alternative to say an ORM like MyBatis?
> It depends in what you need. Please describe your use case.
>
>
>
> --
> Alexey Kuznetsov
>
Re: New version of Web Console released
Posted by Muthu <mu...@gmail.com>.
Thanks Alexey! for the pointers. For the ORM alternate case the use case is
the below (basically today we are thinking of using Ignite with MyBatis
with Ignite being the L2 cache (among other things) & MyBatis being the
persistence framework, the question is can Ignite do the cache with the Web
console's RDBMS Integration or Model support being used to play the role of
the persistence framework so it will be an all Ignite thingy),
1. A way to write DTOs to ignite cache which will then automatically (async
aswell) persist to DB (model/DTO generation, db persistence, etc)
-- This includes insert, update & delete and batch/bulk operations
2. A way to read from ignite cache which will automatically read from DB if
not in cache
-- This includes read based on any predicate (where clause), custom
select sql queries, bulk operations
Regards,
Muthu
On Wed, Jun 7, 2017 at 12:19 AM, Alexey Kuznetsov <ak...@apache.org>
wrote:
> Muthu,
>
> >> Is the web console not part of or deploy-able from the ignite fabric
> distrib
> Yes. It is not part of binary distribution.
> You can build it from sources or use Docker image (see:
> https://hub.docker.com/r/apacheignite/web-console-standalone/tags/)
>
> >> .but i do not find any directory named "modules" under my IGNITE_HOME
> You need to download SOURCE release.
>
>
> >>> Can i download only a trial version from console.gridgain.com ?
> No. console.gridgain.com contains Web Console that based on Apache Ignite
> code base, but with additional features developed by GridGain.
> Please contact GridGain for that.
>
> >> Will i able to use this as an alternative to say an ORM like MyBatis?
> It depends in what you need. Please describe your use case.
>
>
>
> --
> Alexey Kuznetsov
>
Re: New version of Web Console released
Posted by Alexey Kuznetsov <ak...@apache.org>.
Muthu,
>> Is the web console not part of or deploy-able from the ignite fabric
distrib
Yes. It is not part of binary distribution.
You can build it from sources or use Docker image (see:
https://hub.docker.com/r/apacheignite/web-console-standalone/tags/)
>> .but i do not find any directory named "modules" under my IGNITE_HOME
You need to download SOURCE release.
>>> Can i download only a trial version from console.gridgain.com ?
No. console.gridgain.com contains Web Console that based on Apache Ignite
code base, but with additional features developed by GridGain.
Please contact GridGain for that.
>> Will i able to use this as an alternative to say an ORM like MyBatis?
It depends in what you need. Please describe your use case.
--
Alexey Kuznetsov
Re: New version of Web Console released
Posted by Alexey Kuznetsov <ak...@apache.org>.
Muthu,
>> Is the web console not part of or deploy-able from the ignite fabric
distrib
Yes. It is not part of binary distribution.
You can build it from sources or use Docker image (see:
https://hub.docker.com/r/apacheignite/web-console-standalone/tags/)
>> .but i do not find any directory named "modules" under my IGNITE_HOME
You need to download SOURCE release.
>>> Can i download only a trial version from console.gridgain.com ?
No. console.gridgain.com contains Web Console that based on Apache Ignite
code base, but with additional features developed by GridGain.
Please contact GridGain for that.
>> Will i able to use this as an alternative to say an ORM like MyBatis?
It depends in what you need. Please describe your use case.
--
Alexey Kuznetsov
Re: New version of Web Console released
Posted by Muthu <mu...@gmail.com>.
Hi Alexey, Others,
Is the web console not part of or deploy-able from the ignite fabric
distribution?
The doc on build & deploy @
https://apacheignite-tools.readme.io/docs/build-and-deploy#section-prerequisites,
talks about the below...but i do not find any directory named "modules"
under my IGNITE_HOME
Download the following dependencies:
-
For backend:
cd $IGNITE_HOME/modules/web-console/backend
npm install --no-optional
-
For frontend:
cd $IGNITE_HOME/modules/web-console/frontend
npm install --no-optional
Can i download only a trial version from console.gridgain.com ?
Also does this version support the Automatic RDBMS Integration as stated @
https://apacheignite-tools.readme.io/docs/automatic-rdbms-integration?
Will i able to use this as an alternative to say an ORM like MyBatis?
Regards,
Muthu
On Mon, Jun 5, 2017 at 10:44 AM, Denis Magda <dm...@apache.org> wrote:
> Alex K.,
>
> Sounds great! BTW, was this ticket resolved as a part of the release:
> https://issues.apache.org/jira/browse/IGNITE-5303 (supporting multiple
> RDBMS configurations from the wizard)
>
> —
> Denis
>
> On Jun 5, 2017, at 7:54 AM, Alexey Kuznetsov <ak...@apache.org>
> 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 GridGain infrastructure (https://console
> .gridgain.com) where you can give it a try right a way.
>
> NOTE: You may need to refresh page (F5 or Ctrl+R) in order to reload Web
> Console.
>
> *What's new:*
> * Support for Ignite 1.x / Ignite 2.0
> You can configure, query and monitoring Ignite 1.x and Ignite 2.0 from
> single Web Console.
>
> * Improved build with web pack
>
> *Coming soon:*
> * Notifications about Web Console updates!
> Web console will show banner with warning about upcoming updates.
>
> * Support for Ignite 2.1
>
> * Improved stack trace for SQL errors.
>
> Stay tuned for updates!
>
>
> --
> Alexey Kuznetsov
>
>
>
Re: New version of Web Console released
Posted by Alexey Kuznetsov <ak...@apache.org>.
Denis,
>>>Sounds great! BTW, was this ticket resolved as a part of the release:
>>> https://issues.apache.org/jira/browse/IGNITE-5303 (supporting multiple
RDBMS configurations from the wizard)
Yes we fixed this issue, now it is on testing with all major RDBMS.
--
Alexey Kuznetsov
Re: New version of Web Console released
Posted by Muthu <mu...@gmail.com>.
Hi Alexey, Others,
Is the web console not part of or deploy-able from the ignite fabric
distribution?
The doc on build & deploy @
https://apacheignite-tools.readme.io/docs/build-and-deploy#section-prerequisites,
talks about the below...but i do not find any directory named "modules"
under my IGNITE_HOME
Download the following dependencies:
-
For backend:
cd $IGNITE_HOME/modules/web-console/backend
npm install --no-optional
-
For frontend:
cd $IGNITE_HOME/modules/web-console/frontend
npm install --no-optional
Can i download only a trial version from console.gridgain.com ?
Also does this version support the Automatic RDBMS Integration as stated @
https://apacheignite-tools.readme.io/docs/automatic-rdbms-integration?
Will i able to use this as an alternative to say an ORM like MyBatis?
Regards,
Muthu
On Mon, Jun 5, 2017 at 10:44 AM, Denis Magda <dm...@apache.org> wrote:
> Alex K.,
>
> Sounds great! BTW, was this ticket resolved as a part of the release:
> https://issues.apache.org/jira/browse/IGNITE-5303 (supporting multiple
> RDBMS configurations from the wizard)
>
> —
> Denis
>
> On Jun 5, 2017, at 7:54 AM, Alexey Kuznetsov <ak...@apache.org>
> 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 GridGain infrastructure (https://console
> .gridgain.com) where you can give it a try right a way.
>
> NOTE: You may need to refresh page (F5 or Ctrl+R) in order to reload Web
> Console.
>
> *What's new:*
> * Support for Ignite 1.x / Ignite 2.0
> You can configure, query and monitoring Ignite 1.x and Ignite 2.0 from
> single Web Console.
>
> * Improved build with web pack
>
> *Coming soon:*
> * Notifications about Web Console updates!
> Web console will show banner with warning about upcoming updates.
>
> * Support for Ignite 2.1
>
> * Improved stack trace for SQL errors.
>
> Stay tuned for updates!
>
>
> --
> Alexey Kuznetsov
>
>
>
Re: New version of Web Console released
Posted by Alexey Kuznetsov <ak...@apache.org>.
Denis,
>>>Sounds great! BTW, was this ticket resolved as a part of the release:
>>> https://issues.apache.org/jira/browse/IGNITE-5303 (supporting multiple
RDBMS configurations from the wizard)
Yes we fixed this issue, now it is on testing with all major RDBMS.
--
Alexey Kuznetsov
Re: New version of Web Console released
Posted by Denis Magda <dm...@apache.org>.
Alex K.,
Sounds great! BTW, was this ticket resolved as a part of the release:
https://issues.apache.org/jira/browse/IGNITE-5303 <https://issues.apache.org/jira/browse/IGNITE-5303> (supporting multiple RDBMS configurations from the wizard)
—
Denis
> On Jun 5, 2017, at 7:54 AM, Alexey Kuznetsov <ak...@apache.org> 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 GridGain infrastructure (https://console
> .gridgain.com) where you can give it a try right a way.
>
> NOTE: You may need to refresh page (F5 or Ctrl+R) in order to reload Web
> Console.
>
> *What's new:*
> * Support for Ignite 1.x / Ignite 2.0
> You can configure, query and monitoring Ignite 1.x and Ignite 2.0 from
> single Web Console.
>
> * Improved build with web pack
>
> *Coming soon:*
> * Notifications about Web Console updates!
> Web console will show banner with warning about upcoming updates.
>
> * Support for Ignite 2.1
>
> * Improved stack trace for SQL errors.
>
> Stay tuned for updates!
>
>
> --
> Alexey Kuznetsov
Re: New version of Web Console released
Posted by Denis Magda <dm...@apache.org>.
Alex K.,
Sounds great! BTW, was this ticket resolved as a part of the release:
https://issues.apache.org/jira/browse/IGNITE-5303 <https://issues.apache.org/jira/browse/IGNITE-5303> (supporting multiple RDBMS configurations from the wizard)
—
Denis
> On Jun 5, 2017, at 7:54 AM, Alexey Kuznetsov <ak...@apache.org> 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 GridGain infrastructure (https://console
> .gridgain.com) where you can give it a try right a way.
>
> NOTE: You may need to refresh page (F5 or Ctrl+R) in order to reload Web
> Console.
>
> *What's new:*
> * Support for Ignite 1.x / Ignite 2.0
> You can configure, query and monitoring Ignite 1.x and Ignite 2.0 from
> single Web Console.
>
> * Improved build with web pack
>
> *Coming soon:*
> * Notifications about Web Console updates!
> Web console will show banner with warning about upcoming updates.
>
> * Support for Ignite 2.1
>
> * Improved stack trace for SQL errors.
>
> Stay tuned for updates!
>
>
> --
> Alexey Kuznetsov