Re: Adding sqlline tool to Apache Ignite project

[Dmitriy Setrakyan]

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:

> Thought over 127.0.0.1 as a default host once again. The bad thing about
> it is that the user gets a lengthy exception stack trace if Ignite  is not
> running locally and not a small error message.
>
> What are the other opinions on this? Do we want to follow Vladimir’s
> suggestion forcing to set the host name/IP (port is optional) for the sake
> of usability or leaver 127.0.0.1 as default?
>
> —
> Denis
>
> > On Oct 6, 2017, at 12:21 PM, Denis Magda  wrote:
> >
> >> But, we need to support “help” (-h, -help) argument listing all the
> parameters accepted by the tools.
> >
> > Meant accepted by the ignitesql script only such as host name.
> >
> > —
> > Denis
> >
> >> On Oct 6, 2017, at 12:20 PM, Denis Magda  wrote:
> >>
> >> Really nice, could click through the getting started [1] in a minute!
> >>
> >> +1 to rename the script to “ignitesql”. Vladimir’s point makes total
> sense.
> >>
> >> However, tend to disagree that the host has to be requested all the
> times. We never request a configuration or host name for ignite.sh, visor
> or web agent scripts. I would follow this approach that’s excellent for dev
> time.
> >>
> >> But, we need to support “help” (-h, -help) argument listing all the
> parameters accepted by the tools.
> >>
> >> Please consider our feedback and share the next build once it’s ready.
> >>
> >>
> >> [1] https://apacheignite-sql.readme.io/v2.1/docs/getting-started <
> https://apacheignite-sql.readme.io/v2.1/docs/getting-started>
> >>
> >> —
> >> Denis
> >>
> >>> On Oct 6, 2017, at 9:04 AM, Anton Vinogradov 
> wrote:
> >>>
> >>> How about sqlconsole.sh or sqlcmd.sh ?
> >>>
> >>> On Fri, Oct 6, 2017 at 6:04 PM,  wrote:
> >>>
>  I like ignitesql.
> 
>  ⁣D.​
> 
>  On Oct 6, 2017, 4:49 PM, at 4:49 PM, Vladimir Ozerov <
> voze...@gridgain.com>
>  wrote:
> > Denis,
> >
> > Setting default host to 127.0.0.1 is bad idea, because it mean that
> in
> > practice users would have to change the script always. Instead, we
> > should
> > accept host name as argument. This is perfectly fine from usability
> > perspective, most tools work this way (i.e. throw error when started
> > without arguments).
> >
> > Also IMO "ignitedb" is misleading name. Users would like think that
> it
> > is a
> > kind of script to start database, rather than to connect to it. We
> > should
> > think on other names. E.g. "ignitesql".
> >
> > On Fri, Oct 6, 2017 at 5:23 PM, Sergey Kozlov 
> > wrote:
> >
> >> Denis
> >>
> >> The link below has included sqlline. Please take a look:
> >> https://ci.ignite.apache.org/viewLog.html?buildId=875441;
> >> buildTypeId=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
> >> pareVote=artifacts#!1rrb2,-wpvx2aopzexz
> >>
> >> On Thu, Oct 5, 2017 at 7:48 PM, Denis Magda 
> > wrote:
> >>
> >>> Here is the original ticket [1]. Ilya, closed the one created by
> > you as a
> >>> duplicate.
> >>>
> >>> In addition to the tool’s jar inclusion in Ignite’s binary releases
> > let’s
> >>> create a shell script to simplify the connectivity phase:
> >>>
> >>> - name the script as ignitedb.sh for Unix and ignitedb.bat for
> >> Windows.
> >>> -
> >>> - the script uses the following connection string by default:
> > .sqlline
> >>> -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> > --verbose=true
> >>> --showWarnings=true --showNestedErrs=true -u jdbc:ignite:
> >>> thin://127.0.0.1/
> >>>
> >>>
> >>>
> >>> - make up parameters list to adjust Ignite specific part of the
> >>> connection string: Ignite IP and port, streaming mode, etc. The
> > full
> >> list
> >>> of supported parameters is here: https://apacheignite-
> >>> sql.readme.io/docs/jdbc-driver#jdbc-thin-driver
> >>>
> >  jdbc-thin-driver
> >>>
> >>>
> >>>
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-5608
> >>>
> >>> —
> >>> Denis
> >>>
> >>> On Oct 5, 2017, at 9:02 AM, Sergey Kozlov 
> > wrote:
> >>>
> >>> Dmitriy, Denis
> >>>
> >>> We're in progress to add sqlline in upcoming 2.3
> >>>
> >>> On Thu, Oct 5, 2017 at 5:30 PM, Dmitriy Setrakyan
> >   wrote:
> >>> Would be nice to get it in 2.3. This is critical functionality for
> > our
> >>> users and 2.4 seems too far to give anyone comfort.
> >>>
> >>> On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov
> > 
> >>> wrote:
> >>>
> 

Re: Adding sqlline tool to Apache Ignite project

[Dmitriy Setrakyan]

On Fri, Oct 6, 2017 at 9:04 AM, Anton Vinogradov 
wrote:

> How about sqlconsole.sh or sqlcmd.sh ?
>

Shouldn't we have "ignite" in the name?

Re: Identifying grid transactions

[Valentin Kulichenko]

Yakov,

Ideally - all of them :) Or at least those APIs that execute remote
operations (all cache operations, compute, service proxy invocations, ...).
Having an ability to add custom metadata to this kind of operations can be
very valuable for auditing purposes.

-Val

On Thu, Oct 5, 2017 at 8:38 AM, Yakov Zhdanov  wrote:

> >>That's a very useful suggestion. Can it be supported for other APIs as
> >> well, not only transactions?
>
> >> -Val
>
> Val, please clarify. What APIs do you mean?
>
> --Yakov
>

Re: PRIMARY_SYNC+readFromBackup semantics

[Valentin Kulichenko]

Created a ticket: https://issues.apache.org/jira/browse/IGNITE-6575

-Val

On Thu, Oct 5, 2017 at 8:55 AM, Yakov Zhdanov  wrote:

> >>Second of all, it seems that we send a network message from primary node
> to
> local backup, which doesn't make much sense to me and looks like
> unnecessary performance overhead.
>
> This does not work. Remember CLOCK mode for atomic updates? We removed that
> mode. You need globally growing version to make it this way.
>
> As a solution I would suggest to update local copy before completing
> operation future, i.e. on primary node response processing. Val, please
> create a ticket if there is no objections (I would also check if we already
> have this ticket).
>
> Another point is that user can go to another backup (send compute closure)
> and find old value there. To my mind, it would be cool to have an
> opportunity to set write sync mode per operation using
> "withWriteSynchronization()" syntax.
>
> --Yakov
>

[jira] [Created] (IGNITE-6575) IgniteCache#get can return stale value when executed on backup

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-6575:
---

 Summary: IgniteCache#get can return stale value when executed on 
backup
 Key: IGNITE-6575
 URL: https://issues.apache.org/jira/browse/IGNITE-6575
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.2
Reporter: Valentin Kulichenko


If write sync mode is {{PRIMARY_SYNC}} and {{readFromBackup=true}} (both values 
are defaults), calling {{get}} right after {{put}} for the same key in the same 
thread can return stale value. This happens because even local backup is 
updated asynchronously.

This is very confusing behavior for a user, would be good to make sure to 
update local backup synchronously even in {{PRIMARY_SYNC}} mode.

More details here: 
http://apache-ignite-developers.2346864.n4.nabble.com/PRIMARY-SYNC-readFromBackup-semantics-td22900.html



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

Re: Adding sqlline tool to Apache Ignite project

[Denis Magda]

> But, we need to support “help” (-h, -help) argument listing all the 
> parameters accepted by the tools.

Meant accepted by the ignitesql script only such as host name.

—
Denis

> On Oct 6, 2017, at 12:20 PM, Denis Magda  wrote:
> 
> Really nice, could click through the getting started [1] in a minute!
> 
> +1 to rename the script to “ignitesql”. Vladimir’s point makes total sense.
> 
> However, tend to disagree that the host has to be requested all the times. We 
> never request a configuration or host name for ignite.sh, visor or web agent 
> scripts. I would follow this approach that’s excellent for dev time.
> 
> But, we need to support “help” (-h, -help) argument listing all the 
> parameters accepted by the tools.
> 
> Please consider our feedback and share the next build once it’s ready.
> 
> 
> [1] https://apacheignite-sql.readme.io/v2.1/docs/getting-started 
> 
> 
> —
> Denis
> 
>> On Oct 6, 2017, at 9:04 AM, Anton Vinogradov  
>> wrote:
>> 
>> How about sqlconsole.sh or sqlcmd.sh ?
>> 
>> On Fri, Oct 6, 2017 at 6:04 PM,  wrote:
>> 
>>> I like ignitesql.
>>> 
>>> ⁣D.​
>>> 
>>> On Oct 6, 2017, 4:49 PM, at 4:49 PM, Vladimir Ozerov 
>>> wrote:
 Denis,
 
 Setting default host to 127.0.0.1 is bad idea, because it mean that in
 practice users would have to change the script always. Instead, we
 should
 accept host name as argument. This is perfectly fine from usability
 perspective, most tools work this way (i.e. throw error when started
 without arguments).
 
 Also IMO "ignitedb" is misleading name. Users would like think that it
 is a
 kind of script to start database, rather than to connect to it. We
 should
 think on other names. E.g. "ignitesql".
 
 On Fri, Oct 6, 2017 at 5:23 PM, Sergey Kozlov 
 wrote:
 
> Denis
> 
> The link below has included sqlline. Please take a look:
> https://ci.ignite.apache.org/viewLog.html?buildId=875441;
> buildTypeId=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
> pareVote=artifacts#!1rrb2,-wpvx2aopzexz
> 
> On Thu, Oct 5, 2017 at 7:48 PM, Denis Magda 
 wrote:
> 
>> Here is the original ticket [1]. Ilya, closed the one created by
 you as a
>> duplicate.
>> 
>> In addition to the tool’s jar inclusion in Ignite’s binary releases
 let’s
>> create a shell script to simplify the connectivity phase:
>> 
>>  - name the script as ignitedb.sh for Unix and ignitedb.bat for
> Windows.
>>  -
>>  - the script uses the following connection string by default:
 .sqlline
>>  -d org.apache.ignite.IgniteJdbcThinDriver --color=true
 --verbose=true
>>  --showWarnings=true --showNestedErrs=true -u jdbc:ignite:
>>  thin://127.0.0.1/
>> 
>> 
>> 
>>  - make up parameters list to adjust Ignite specific part of the
>>  connection string: Ignite IP and port, streaming mode, etc. The
 full
> list
>>  of supported parameters is here: https://apacheignite-
>>  sql.readme.io/docs/jdbc-driver#jdbc-thin-driver
>> 
 > 
>> 
>> 
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-5608
>> 
>> —
>> Denis
>> 
>> On Oct 5, 2017, at 9:02 AM, Sergey Kozlov 
 wrote:
>> 
>> Dmitriy, Denis
>> 
>> We're in progress to add sqlline in upcoming 2.3
>> 
>> On Thu, Oct 5, 2017 at 5:30 PM, Dmitriy Setrakyan
 >> wrote:
>> Would be nice to get it in 2.3. This is critical functionality for
 our
>> users and 2.4 seems too far to give anyone comfort.
>> 
>> On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov
 
>> wrote:
>> 
>>> Guys,
>>> 
>>> I've created the ticket for 2.4 release:
>>> https://issues.apache.org/jira/browse/IGNITE-6561
>>> 
>>> 2017-08-30 22:21 GMT+03:00 Julian Hyde :
>>> 
 Denis,
 
 I’m glad you’re thinking of using SQLLine. Under the BSD
 license, you
 don’t need my permission to distribute, but I grant that
 permission.
 
 Drill, Phoenix and Calcite already distribute SQLLine, so
 Ignite is
> in
 good company.
 
 If you need extensions, please discuss on the dev list, or open
 a
>> GitHub
 case or pull request. SQLLine operates in the usual way for a
 GitHub
 project. It’s unlikely that you’ll need Ignite-specific
 extensions —
 SQLLine just exposes what comes through the JDBC driver — but
 we can
 discuss if the need arises. The Hive project forked SQLLine
 into its

Re: Adding sqlline tool to Apache Ignite project

[Denis Magda]

Really nice, could click through the getting started [1] in a minute!

+1 to rename the script to “ignitesql”. Vladimir’s point makes total sense.

However, tend to disagree that the host has to be requested all the times. We 
never request a configuration or host name for ignite.sh, visor or web agent 
scripts. I would follow this approach that’s excellent for dev time.

But, we need to support “help” (-h, -help) argument listing all the parameters 
accepted by the tools.

Please consider our feedback and share the next build once it’s ready.


[1] https://apacheignite-sql.readme.io/v2.1/docs/getting-started 


—
Denis

> On Oct 6, 2017, at 9:04 AM, Anton Vinogradov  wrote:
> 
> How about sqlconsole.sh or sqlcmd.sh ?
> 
> On Fri, Oct 6, 2017 at 6:04 PM,  wrote:
> 
>> I like ignitesql.
>> 
>> ⁣D.​
>> 
>> On Oct 6, 2017, 4:49 PM, at 4:49 PM, Vladimir Ozerov 
>> wrote:
>>> Denis,
>>> 
>>> Setting default host to 127.0.0.1 is bad idea, because it mean that in
>>> practice users would have to change the script always. Instead, we
>>> should
>>> accept host name as argument. This is perfectly fine from usability
>>> perspective, most tools work this way (i.e. throw error when started
>>> without arguments).
>>> 
>>> Also IMO "ignitedb" is misleading name. Users would like think that it
>>> is a
>>> kind of script to start database, rather than to connect to it. We
>>> should
>>> think on other names. E.g. "ignitesql".
>>> 
>>> On Fri, Oct 6, 2017 at 5:23 PM, Sergey Kozlov 
>>> wrote:
>>> 
 Denis
 
 The link below has included sqlline. Please take a look:
 https://ci.ignite.apache.org/viewLog.html?buildId=875441;
 buildTypeId=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
 pareVote=artifacts#!1rrb2,-wpvx2aopzexz
 
 On Thu, Oct 5, 2017 at 7:48 PM, Denis Magda 
>>> wrote:
 
> Here is the original ticket [1]. Ilya, closed the one created by
>>> you as a
> duplicate.
> 
> In addition to the tool’s jar inclusion in Ignite’s binary releases
>>> let’s
> create a shell script to simplify the connectivity phase:
> 
>   - name the script as ignitedb.sh for Unix and ignitedb.bat for
 Windows.
>   -
>   - the script uses the following connection string by default:
>>> .sqlline
>   -d org.apache.ignite.IgniteJdbcThinDriver --color=true
>>> --verbose=true
>   --showWarnings=true --showNestedErrs=true -u jdbc:ignite:
>   thin://127.0.0.1/
> 
> 
> 
>   - make up parameters list to adjust Ignite specific part of the
>   connection string: Ignite IP and port, streaming mode, etc. The
>>> full
 list
>   of supported parameters is here: https://apacheignite-
>   sql.readme.io/docs/jdbc-driver#jdbc-thin-driver
> 
>>>  
> 
> 
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-5608
> 
> —
> Denis
> 
> On Oct 5, 2017, at 9:02 AM, Sergey Kozlov 
>>> wrote:
> 
> Dmitriy, Denis
> 
> We're in progress to add sqlline in upcoming 2.3
> 
> On Thu, Oct 5, 2017 at 5:30 PM, Dmitriy Setrakyan
>>> > wrote:
> Would be nice to get it in 2.3. This is critical functionality for
>>> our
> users and 2.4 seems too far to give anyone comfort.
> 
> On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov
>>> 
> wrote:
> 
>> Guys,
>> 
>> I've created the ticket for 2.4 release:
>> https://issues.apache.org/jira/browse/IGNITE-6561
>> 
>> 2017-08-30 22:21 GMT+03:00 Julian Hyde :
>> 
>>> Denis,
>>> 
>>> I’m glad you’re thinking of using SQLLine. Under the BSD
>>> license, you
>>> don’t need my permission to distribute, but I grant that
>>> permission.
>>> 
>>> Drill, Phoenix and Calcite already distribute SQLLine, so
>>> Ignite is
 in
>>> good company.
>>> 
>>> If you need extensions, please discuss on the dev list, or open
>>> a
> GitHub
>>> case or pull request. SQLLine operates in the usual way for a
>>> GitHub
>>> project. It’s unlikely that you’ll need Ignite-specific
>>> extensions —
>>> SQLLine just exposes what comes through the JDBC driver — but
>>> we can
>>> discuss if the need arises. The Hive project forked SQLLine
>>> into its
> own
>>> Beeline module and I’d like to avoid a repeat of that.
>>> 
>>> Julian
>>> 
 On Aug 29, 2017, at 6:35 PM, Denis Magda 
 wrote:
 
 Igniters,
 
 Let me introduce Julian Hyde [1], creator of SQLLine tool and
>>> our
>> Apache
>>> mate,
 
 Julian,
 
 Please grant that Apache Ignite 

[GitHub] ignite pull request #2816: IGNITE-2766 Essais: Opportunistic reopen cache.

[alamar]

GitHub user alamar opened a pull request:

https://github.com/apache/ignite/pull/2816

IGNITE-2766 Essais: Opportunistic reopen cache.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2766

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2816.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2816


commit 3e8d3e8d756290e749a3f2d2a1a4deba97743a26
Author: Ilya Kasnacheev 
Date:   2017-10-06T17:19:56Z

IGNITE-2766 Essais: Opportunistic reopen cache.




---

Re: Adding sqlline tool to Apache Ignite project

[Anton Vinogradov]

How about sqlconsole.sh or sqlcmd.sh ?

On Fri, Oct 6, 2017 at 6:04 PM,  wrote:

> I like ignitesql.
>
> ⁣D.​
>
> On Oct 6, 2017, 4:49 PM, at 4:49 PM, Vladimir Ozerov 
> wrote:
> >Denis,
> >
> >Setting default host to 127.0.0.1 is bad idea, because it mean that in
> >practice users would have to change the script always. Instead, we
> >should
> >accept host name as argument. This is perfectly fine from usability
> >perspective, most tools work this way (i.e. throw error when started
> >without arguments).
> >
> >Also IMO "ignitedb" is misleading name. Users would like think that it
> >is a
> >kind of script to start database, rather than to connect to it. We
> >should
> >think on other names. E.g. "ignitesql".
> >
> >On Fri, Oct 6, 2017 at 5:23 PM, Sergey Kozlov 
> >wrote:
> >
> >> Denis
> >>
> >> The link below has included sqlline. Please take a look:
> >> https://ci.ignite.apache.org/viewLog.html?buildId=875441;
> >> buildTypeId=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
> >> pareVote=artifacts#!1rrb2,-wpvx2aopzexz
> >>
> >> On Thu, Oct 5, 2017 at 7:48 PM, Denis Magda 
> >wrote:
> >>
> >> > Here is the original ticket [1]. Ilya, closed the one created by
> >you as a
> >> > duplicate.
> >> >
> >> > In addition to the tool’s jar inclusion in Ignite’s binary releases
> >let’s
> >> > create a shell script to simplify the connectivity phase:
> >> >
> >> >- name the script as ignitedb.sh for Unix and ignitedb.bat for
> >> Windows.
> >> >-
> >> >- the script uses the following connection string by default:
> >.sqlline
> >> >-d org.apache.ignite.IgniteJdbcThinDriver --color=true
> >--verbose=true
> >> >--showWarnings=true --showNestedErrs=true -u jdbc:ignite:
> >> >thin://127.0.0.1/
> >> >
> >> >
> >> >
> >> >- make up parameters list to adjust Ignite specific part of the
> >> >connection string: Ignite IP and port, streaming mode, etc. The
> >full
> >> list
> >> >of supported parameters is here: https://apacheignite-
> >> >sql.readme.io/docs/jdbc-driver#jdbc-thin-driver
> >> >
> > >> >
> >> >
> >> >
> >> >
> >> > [1] https://issues.apache.org/jira/browse/IGNITE-5608
> >> >
> >> > —
> >> > Denis
> >> >
> >> > On Oct 5, 2017, at 9:02 AM, Sergey Kozlov 
> >wrote:
> >> >
> >> > Dmitriy, Denis
> >> >
> >> > We're in progress to add sqlline in upcoming 2.3
> >> >
> >> > On Thu, Oct 5, 2017 at 5:30 PM, Dmitriy Setrakyan
> > >> > > wrote:
> >> > Would be nice to get it in 2.3. This is critical functionality for
> >our
> >> > users and 2.4 seems too far to give anyone comfort.
> >> >
> >> > On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov
> >
> >> > wrote:
> >> >
> >> > > Guys,
> >> > >
> >> > > I've created the ticket for 2.4 release:
> >> > > https://issues.apache.org/jira/browse/IGNITE-6561
> >> > >
> >> > > 2017-08-30 22:21 GMT+03:00 Julian Hyde :
> >> > >
> >> > > > Denis,
> >> > > >
> >> > > > I’m glad you’re thinking of using SQLLine. Under the BSD
> >license, you
> >> > > > don’t need my permission to distribute, but I grant that
> >permission.
> >> > > >
> >> > > > Drill, Phoenix and Calcite already distribute SQLLine, so
> >Ignite is
> >> in
> >> > > > good company.
> >> > > >
> >> > > > If you need extensions, please discuss on the dev list, or open
> >a
> >> > GitHub
> >> > > > case or pull request. SQLLine operates in the usual way for a
> >GitHub
> >> > > > project. It’s unlikely that you’ll need Ignite-specific
> >extensions —
> >> > > > SQLLine just exposes what comes through the JDBC driver — but
> >we can
> >> > > > discuss if the need arises. The Hive project forked SQLLine
> >into its
> >> > own
> >> > > > Beeline module and I’d like to avoid a repeat of that.
> >> > > >
> >> > > > Julian
> >> > > >
> >> > > > > On Aug 29, 2017, at 6:35 PM, Denis Magda 
> >> wrote:
> >> > > > >
> >> > > > > Igniters,
> >> > > > >
> >> > > > > Let me introduce Julian Hyde [1], creator of SQLLine tool and
> >our
> >> > > Apache
> >> > > > mate,
> >> > > > >
> >> > > > > Julian,
> >> > > > >
> >> > > > > Please grant that Apache Ignite community a permission to
> >include
> >> > > > SQLLine [2] it in every Ignite deliverable (source, binary).
> >It’s
> >> > planned
> >> > > > to suggest the tool as a default command line SQL utility for
> >Ignite
> >> > > > clusters. SQLLite and Ignite usage will also be documented on
> >> Ignite’s
> >> > > > technical documentation.
> >> > > > >
> >> > > > > [1] https://people.apache.org/~jhyde/ <
> >> https://people.apache.org/~jh
> >> > > yde/
> >> > > > >
> >> > > > > [2] https://github.com/julianhyde/sqlline
> > >> > > > julianhyde/sqlline>
> >> > > > >
> >> > > > > —
> >> > > > > Denis
> >> > > > >
> >> > > > >> On Aug 25, 2017, at 9:17 AM, Denis Magda 

[jira] [Created] (IGNITE-6573) SQL: Document WRAP_KEY and WRAP_VALUE commands

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6573:
---

 Summary: SQL: Document WRAP_KEY and WRAP_VALUE commands
 Key: IGNITE-6573
 URL: https://issues.apache.org/jira/browse/IGNITE-6573
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.3






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

[GitHub] ignite pull request #2784: IGNITE-6054

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2784


---

Re: Adding sqlline tool to Apache Ignite project

[dsetrakyan]

I like ignitesql.

⁣D.​

On Oct 6, 2017, 4:49 PM, at 4:49 PM, Vladimir Ozerov  
wrote:
>Denis,
>
>Setting default host to 127.0.0.1 is bad idea, because it mean that in
>practice users would have to change the script always. Instead, we
>should
>accept host name as argument. This is perfectly fine from usability
>perspective, most tools work this way (i.e. throw error when started
>without arguments).
>
>Also IMO "ignitedb" is misleading name. Users would like think that it
>is a
>kind of script to start database, rather than to connect to it. We
>should
>think on other names. E.g. "ignitesql".
>
>On Fri, Oct 6, 2017 at 5:23 PM, Sergey Kozlov 
>wrote:
>
>> Denis
>>
>> The link below has included sqlline. Please take a look:
>> https://ci.ignite.apache.org/viewLog.html?buildId=875441;
>> buildTypeId=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
>> pareVote=artifacts#!1rrb2,-wpvx2aopzexz
>>
>> On Thu, Oct 5, 2017 at 7:48 PM, Denis Magda 
>wrote:
>>
>> > Here is the original ticket [1]. Ilya, closed the one created by
>you as a
>> > duplicate.
>> >
>> > In addition to the tool’s jar inclusion in Ignite’s binary releases
>let’s
>> > create a shell script to simplify the connectivity phase:
>> >
>> >- name the script as ignitedb.sh for Unix and ignitedb.bat for
>> Windows.
>> >-
>> >- the script uses the following connection string by default:
>.sqlline
>> >-d org.apache.ignite.IgniteJdbcThinDriver --color=true
>--verbose=true
>> >--showWarnings=true --showNestedErrs=true -u jdbc:ignite:
>> >thin://127.0.0.1/
>> >
>> >
>> >
>> >- make up parameters list to adjust Ignite specific part of the
>> >connection string: Ignite IP and port, streaming mode, etc. The
>full
>> list
>> >of supported parameters is here: https://apacheignite-
>> >sql.readme.io/docs/jdbc-driver#jdbc-thin-driver
>> >
>> >
>> >
>> >
>> >
>> > [1] https://issues.apache.org/jira/browse/IGNITE-5608
>> >
>> > —
>> > Denis
>> >
>> > On Oct 5, 2017, at 9:02 AM, Sergey Kozlov 
>wrote:
>> >
>> > Dmitriy, Denis
>> >
>> > We're in progress to add sqlline in upcoming 2.3
>> >
>> > On Thu, Oct 5, 2017 at 5:30 PM, Dmitriy Setrakyan
>> > > wrote:
>> > Would be nice to get it in 2.3. This is critical functionality for
>our
>> > users and 2.4 seems too far to give anyone comfort.
>> >
>> > On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov
>
>> > wrote:
>> >
>> > > Guys,
>> > >
>> > > I've created the ticket for 2.4 release:
>> > > https://issues.apache.org/jira/browse/IGNITE-6561
>> > >
>> > > 2017-08-30 22:21 GMT+03:00 Julian Hyde :
>> > >
>> > > > Denis,
>> > > >
>> > > > I’m glad you’re thinking of using SQLLine. Under the BSD
>license, you
>> > > > don’t need my permission to distribute, but I grant that
>permission.
>> > > >
>> > > > Drill, Phoenix and Calcite already distribute SQLLine, so
>Ignite is
>> in
>> > > > good company.
>> > > >
>> > > > If you need extensions, please discuss on the dev list, or open
>a
>> > GitHub
>> > > > case or pull request. SQLLine operates in the usual way for a
>GitHub
>> > > > project. It’s unlikely that you’ll need Ignite-specific
>extensions —
>> > > > SQLLine just exposes what comes through the JDBC driver — but
>we can
>> > > > discuss if the need arises. The Hive project forked SQLLine
>into its
>> > own
>> > > > Beeline module and I’d like to avoid a repeat of that.
>> > > >
>> > > > Julian
>> > > >
>> > > > > On Aug 29, 2017, at 6:35 PM, Denis Magda 
>> wrote:
>> > > > >
>> > > > > Igniters,
>> > > > >
>> > > > > Let me introduce Julian Hyde [1], creator of SQLLine tool and
>our
>> > > Apache
>> > > > mate,
>> > > > >
>> > > > > Julian,
>> > > > >
>> > > > > Please grant that Apache Ignite community a permission to
>include
>> > > > SQLLine [2] it in every Ignite deliverable (source, binary).
>It’s
>> > planned
>> > > > to suggest the tool as a default command line SQL utility for
>Ignite
>> > > > clusters. SQLLite and Ignite usage will also be documented on
>> Ignite’s
>> > > > technical documentation.
>> > > > >
>> > > > > [1] https://people.apache.org/~jhyde/ <
>> https://people.apache.org/~jh
>> > > yde/
>> > > > >
>> > > > > [2] https://github.com/julianhyde/sqlline
>> > > > julianhyde/sqlline>
>> > > > >
>> > > > > —
>> > > > > Denis
>> > > > >
>> > > > >> On Aug 25, 2017, at 9:17 AM, Denis Magda > >  > > > > dma...@apache.org>> wrote:
>> > > > >>
>> > > > >> Hi Ilya,
>> > > > >>
>> > > > >> Thanks for the clarification! Referring to the page shared
>by you
>> > [1]
>> > > > if we need to get author’s consent in a written form:
>> > > > >>
>> > > > >> A permissive license similar to the BSD 2-Clause License,
>but
>> with a
>> > > > 3rd clause that prohibits others from using the name of the

Re: Adding sqlline tool to Apache Ignite project

[Vladimir Ozerov]

Denis,

Setting default host to 127.0.0.1 is bad idea, because it mean that in
practice users would have to change the script always. Instead, we should
accept host name as argument. This is perfectly fine from usability
perspective, most tools work this way (i.e. throw error when started
without arguments).

Also IMO "ignitedb" is misleading name. Users would like think that it is a
kind of script to start database, rather than to connect to it. We should
think on other names. E.g. "ignitesql".

On Fri, Oct 6, 2017 at 5:23 PM, Sergey Kozlov  wrote:

> Denis
>
> The link below has included sqlline. Please take a look:
> https://ci.ignite.apache.org/viewLog.html?buildId=875441;
> buildTypeId=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
> pareVote=artifacts#!1rrb2,-wpvx2aopzexz
>
> On Thu, Oct 5, 2017 at 7:48 PM, Denis Magda  wrote:
>
> > Here is the original ticket [1]. Ilya, closed the one created by you as a
> > duplicate.
> >
> > In addition to the tool’s jar inclusion in Ignite’s binary releases let’s
> > create a shell script to simplify the connectivity phase:
> >
> >- name the script as ignitedb.sh for Unix and ignitedb.bat for
> Windows.
> >-
> >- the script uses the following connection string by default: .sqlline
> >-d org.apache.ignite.IgniteJdbcThinDriver --color=true --verbose=true
> >--showWarnings=true --showNestedErrs=true -u jdbc:ignite:
> >thin://127.0.0.1/
> >
> >
> >
> >- make up parameters list to adjust Ignite specific part of the
> >connection string: Ignite IP and port, streaming mode, etc. The full
> list
> >of supported parameters is here: https://apacheignite-
> >sql.readme.io/docs/jdbc-driver#jdbc-thin-driver
> > >
> >
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-5608
> >
> > —
> > Denis
> >
> > On Oct 5, 2017, at 9:02 AM, Sergey Kozlov  wrote:
> >
> > Dmitriy, Denis
> >
> > We're in progress to add sqlline in upcoming 2.3
> >
> > On Thu, Oct 5, 2017 at 5:30 PM, Dmitriy Setrakyan  > > wrote:
> > Would be nice to get it in 2.3. This is critical functionality for our
> > users and 2.4 seems too far to give anyone comfort.
> >
> > On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov 
> > wrote:
> >
> > > Guys,
> > >
> > > I've created the ticket for 2.4 release:
> > > https://issues.apache.org/jira/browse/IGNITE-6561
> > >
> > > 2017-08-30 22:21 GMT+03:00 Julian Hyde :
> > >
> > > > Denis,
> > > >
> > > > I’m glad you’re thinking of using SQLLine. Under the BSD license, you
> > > > don’t need my permission to distribute, but I grant that permission.
> > > >
> > > > Drill, Phoenix and Calcite already distribute SQLLine, so Ignite is
> in
> > > > good company.
> > > >
> > > > If you need extensions, please discuss on the dev list, or open a
> > GitHub
> > > > case or pull request. SQLLine operates in the usual way for a GitHub
> > > > project. It’s unlikely that you’ll need Ignite-specific extensions —
> > > > SQLLine just exposes what comes through the JDBC driver — but we can
> > > > discuss if the need arises. The Hive project forked SQLLine into its
> > own
> > > > Beeline module and I’d like to avoid a repeat of that.
> > > >
> > > > Julian
> > > >
> > > > > On Aug 29, 2017, at 6:35 PM, Denis Magda 
> wrote:
> > > > >
> > > > > Igniters,
> > > > >
> > > > > Let me introduce Julian Hyde [1], creator of SQLLine tool and our
> > > Apache
> > > > mate,
> > > > >
> > > > > Julian,
> > > > >
> > > > > Please grant that Apache Ignite community a permission to include
> > > > SQLLine [2] it in every Ignite deliverable (source, binary). It’s
> > planned
> > > > to suggest the tool as a default command line SQL utility for Ignite
> > > > clusters. SQLLite and Ignite usage will also be documented on
> Ignite’s
> > > > technical documentation.
> > > > >
> > > > > [1] https://people.apache.org/~jhyde/ <
> https://people.apache.org/~jh
> > > yde/
> > > > >
> > > > > [2] https://github.com/julianhyde/sqlline  > > > julianhyde/sqlline>
> > > > >
> > > > > —
> > > > > Denis
> > > > >
> > > > >> On Aug 25, 2017, at 9:17 AM, Denis Magda  >   > > > dma...@apache.org>> wrote:
> > > > >>
> > > > >> Hi Ilya,
> > > > >>
> > > > >> Thanks for the clarification! Referring to the page shared by you
> > [1]
> > > > if we need to get author’s consent in a written form:
> > > > >>
> > > > >> A permissive license similar to the BSD 2-Clause License, but
> with a
> > > > 3rd clause that prohibits others from using the name of the project
> or
> > > its
> > > > contributors to promote derived products without written consent.
> > > > >>
> > > > >> [1] https://github.com/julianhyde/sqlline/blob/master/LICENSE <
> > > > https://github.com/julianhyde/sqlline/blob/master/LICENSE> <
> > > > 

Re: Adding sqlline tool to Apache Ignite project

[Sergey Kozlov]

Denis

The link below has included sqlline. Please take a look:
https://ci.ignite.apache.org/viewLog.html?buildId=875441=IgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote=artifacts#!1rrb2,-wpvx2aopzexz

On Thu, Oct 5, 2017 at 7:48 PM, Denis Magda  wrote:

> Here is the original ticket [1]. Ilya, closed the one created by you as a
> duplicate.
>
> In addition to the tool’s jar inclusion in Ignite’s binary releases let’s
> create a shell script to simplify the connectivity phase:
>
>- name the script as ignitedb.sh for Unix and ignitedb.bat for Windows.
>-
>- the script uses the following connection string by default: .sqlline
>-d org.apache.ignite.IgniteJdbcThinDriver --color=true --verbose=true
>--showWarnings=true --showNestedErrs=true -u jdbc:ignite:
>thin://127.0.0.1/
>
>
>
>- make up parameters list to adjust Ignite specific part of the
>connection string: Ignite IP and port, streaming mode, etc. The full list
>of supported parameters is here: https://apacheignite-
>sql.readme.io/docs/jdbc-driver#jdbc-thin-driver
>
>
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-5608
>
> —
> Denis
>
> On Oct 5, 2017, at 9:02 AM, Sergey Kozlov  wrote:
>
> Dmitriy, Denis
>
> We're in progress to add sqlline in upcoming 2.3
>
> On Thu, Oct 5, 2017 at 5:30 PM, Dmitriy Setrakyan  > wrote:
> Would be nice to get it in 2.3. This is critical functionality for our
> users and 2.4 seems too far to give anyone comfort.
>
> On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov 
> wrote:
>
> > Guys,
> >
> > I've created the ticket for 2.4 release:
> > https://issues.apache.org/jira/browse/IGNITE-6561
> >
> > 2017-08-30 22:21 GMT+03:00 Julian Hyde :
> >
> > > Denis,
> > >
> > > I’m glad you’re thinking of using SQLLine. Under the BSD license, you
> > > don’t need my permission to distribute, but I grant that permission.
> > >
> > > Drill, Phoenix and Calcite already distribute SQLLine, so Ignite is in
> > > good company.
> > >
> > > If you need extensions, please discuss on the dev list, or open a
> GitHub
> > > case or pull request. SQLLine operates in the usual way for a GitHub
> > > project. It’s unlikely that you’ll need Ignite-specific extensions —
> > > SQLLine just exposes what comes through the JDBC driver — but we can
> > > discuss if the need arises. The Hive project forked SQLLine into its
> own
> > > Beeline module and I’d like to avoid a repeat of that.
> > >
> > > Julian
> > >
> > > > On Aug 29, 2017, at 6:35 PM, Denis Magda  wrote:
> > > >
> > > > Igniters,
> > > >
> > > > Let me introduce Julian Hyde [1], creator of SQLLine tool and our
> > Apache
> > > mate,
> > > >
> > > > Julian,
> > > >
> > > > Please grant that Apache Ignite community a permission to include
> > > SQLLine [2] it in every Ignite deliverable (source, binary). It’s
> planned
> > > to suggest the tool as a default command line SQL utility for Ignite
> > > clusters. SQLLite and Ignite usage will also be documented on Ignite’s
> > > technical documentation.
> > > >
> > > > [1] https://people.apache.org/~jhyde/  > yde/
> > > >
> > > > [2] https://github.com/julianhyde/sqlline  > > julianhyde/sqlline>
> > > >
> > > > —
> > > > Denis
> > > >
> > > >> On Aug 25, 2017, at 9:17 AM, Denis Magda    > > dma...@apache.org>> wrote:
> > > >>
> > > >> Hi Ilya,
> > > >>
> > > >> Thanks for the clarification! Referring to the page shared by you
> [1]
> > > if we need to get author’s consent in a written form:
> > > >>
> > > >> A permissive license similar to the BSD 2-Clause License, but with a
> > > 3rd clause that prohibits others from using the name of the project or
> > its
> > > contributors to promote derived products without written consent.
> > > >>
> > > >> [1] https://github.com/julianhyde/sqlline/blob/master/LICENSE <
> > > https://github.com/julianhyde/sqlline/blob/master/LICENSE> <
> > > https://github.com/julianhyde/sqlline/blob/master/LICENSE <
> > > https://github.com/julianhyde/sqlline/blob/master/LICENSE>>
> > > >>
> > > >> I’ll reach out the author requesting the permit.
> > > >>
> > > >> —
> > > >> Denis
> > > >>
> > > >>> On Aug 25, 2017, at 9:12 AM, Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com > wrote:
> > > >>>
> > > >>> Hi Denis,
> > > >>>
> > > >>> There are two kinds of BSD license, 3-clause and 4-clause. The
> > > difference
> > > >>> between them is advertising clause:
> > > >>>
> > > >>> "3. All advertising materials mentioning features or use of this
> > > software
> > > >>> must display the following acknowledgement: This product includes
> > > software
> > > >>> developed by the University of California, Berkeley and its
> > > contributors."
> > > >>>
> > > >>> which is causing 

[jira] [Created] (IGNITE-6571) Service not found exception when calling service method before initialization finished

[Denis Mekhanikov (JIRA)]

Denis Mekhanikov created IGNITE-6571:


 Summary: Service not found exception when calling service method 
before initialization finished
 Key: IGNITE-6571
 URL: https://issues.apache.org/jira/browse/IGNITE-6571
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Mekhanikov
Priority: Minor


When trying to call a method of a service after its assignment is written to 
cache, but before initialization is complete, then the following exception 
appears in log:

{noformat}
[2017-10-06 16:33:14,688][ERROR][sys-#37%null%][GridTaskWorker] Failed to 
obtain remote job result policy for result from ComputeTask.result(..) method 
(will fail the whole task): GridJobResultImpl [job=C2 [c=ServiceProxyCallable 
[mtdName=foo, svcName=testService, ignite=null]], sib=GridJobSiblingImpl 
[sesId=1f1d3e1fe51-1d90f286-d1f5-452b-8e1e-621f218d0e3e, 
jobId=3f1d3e1fe51-1d90f286-d1f5-452b-8e1e-621f218d0e3e, 
nodeId=037457d8-e2d3-434b-8d34-70f152a3e777, isJobDone=false], 
jobCtx=GridJobContextImpl 
[jobId=3f1d3e1fe51-1d90f286-d1f5-452b-8e1e-621f218d0e3e, timeoutObj=null, 
attrs={}], node=TcpDiscoveryNode [id=037457d8-e2d3-434b-8d34-70f152a3e777, 
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.25.4.149], 
sockAddrs=[/0:0:0:0:0:0:0:1%lo:47501, /127.0.0.1:47501, 
latitude.gridgain.local/172.25.4.149:47501], discPort=47501, order=17, 
intOrder=10, lastExchangeTime=1507296794313, loc=false, 
ver=2.1.0#19700101-sha1:, isClient=false], ex=class 
o.a.i.IgniteException: Service not found: testService, hasRes=true, 
isCancelled=false, isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw user exception 
(override or implement ComputeTask.result(..) method if you would like to have 
automatic failover for this exception).
at 
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1027)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1020)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6640)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1020)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:838)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1066)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1301)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteException: Service not found: 
testService
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1850)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6608)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908)
... 7 more
Caused by: class 
org.apache.ignite.internal.processors.service.GridServiceNotFoundException: 
Service not found: testService
at 
org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:408)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1847)
... 14 more
{noformat}

After that method call waits for initialization to finish and returns 
successfully. Exception in log looks misleading and makes people think that 
something went wrong, but actually everything works as 

[GitHub] ignite pull request #2815: IGNITE-6568 cache descriptor SQL attribute store/...

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

https://github.com/apache/ignite/pull/2815

IGNITE-6568 cache descriptor SQL attribute store/restore fix



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-6568

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2815.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2815


commit 150afd3e88ba2f9151121e35ec6829e3ec03df34
Author: Alexander Paschenko 
Date:   2017-10-06T12:17:19Z

IGNITE-6568 cache descriptor SQL attribute store/restore fix




---

[GitHub] ignite pull request #2814: Ignite 2.1.6

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

https://github.com/apache/ignite/pull/2814

Ignite 2.1.6



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.6

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2814.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2814


commit 2d39bab7e8c40a179fdd0c30b492a53fe2142ba0
Author: Alexey Kuznetsov 
Date:   2017-08-21T11:42:08Z

IGNITE-6127 Implemented GZip data between web-agent and web server.
(cherry picked from commit 90f4d4d)

commit 324915f37285e81b872e14a5c13a066258302bd5
Author: Ilya Lantukh 
Date:   2017-08-21T11:46:48Z

ignite-6096: Fixed races on partition evict (backport).

commit 446e1845672378c4008ad207c3d945fbd236097b
Author: Ilya Lantukh 
Date:   2017-08-21T11:47:13Z

Merge remote-tracking branch 'community/ignite-2.1.4' into ignite-2.1.4

commit c3aa151698f82e46b97052a2189ecfdf11a58f37
Author: sboikov 
Date:   2017-07-24T08:47:16Z

Test for cache partitions state, fix for client cache start.

(cherry picked from commit aeb9336b3b161ddfff73f17e41cd453409b84a16)

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheDatabaseSharedManager.java
#   
modules/core/src/test/java/org/apache/ignite/testsuites/IgniteCacheTestSuite6.java
#   
modules/core/src/test/java/org/apache/ignite/testsuites/IgnitePdsTestSuite.java

commit 270e2b260d3f0519d6f8ab5c2465a84b4c0a6327
Author: sboikov 
Date:   2017-07-27T09:50:37Z

Tried to simplify GridDhtAtomicCache.updateAllAsyncInternal0.

(cherry picked from commit 5704e39)

commit f34ef163359bde62865246856a705e09b92c23e2
Author: sboikov 
Date:   2017-07-27T10:21:14Z

Removed unused methods from IgniteThreadPoolExecutor.

(cherry picked from commit 2574beb)

commit 4bfe699e79fcf34afd62a9bb3a356af2d89d9cc9
Author: sboikov 
Date:   2017-07-27T10:57:11Z

Added related GridIoPolicy in IgniteThread.

(cherry picked from commit 3a3650f)

commit 93eb78f62322ce32900efd430a489afee078dd89
Author: sboikov 
Date:   2017-07-27T12:25:06Z

Minor (added more clear method IgniteTxHandler.prepareNearTxLocal).

(cherry picked from commit e9a0d69)

commit e0fe1c3ca0df4ae51dee84ce5d23eb6292cdac22
Author: sboikov 
Date:   2017-07-28T07:25:16Z

ignite-5858 Fixed affinity initialization on new coordinator (broken in 
aeb9336b3b161ddfff73f17e41cd453409b84a16).

(cherry picked from commit b698bbf)

commit 8d51fb95329aede1ae733b368c68ffe5528e21e6
Author: Alexey Kuznetsov 
Date:   2017-08-21T12:09:08Z

IGNITE-6104 Fixed link.
(cherry picked from commit e678c81)

commit 3b613407c056c01a4eda0c77612a08b8468886d5
Author: Alexey Goncharuk 
Date:   2017-08-02T08:25:08Z

IGNITE-5757 - Rent partitions on exchange completion

(cherry picked from commit c6fbe2d)

commit 762b533d3666903dc4119b5a5252373354bb98e1
Author: sboikov 
Date:   2017-08-21T12:22:18Z

Merge remote-tracking branch 'community/ignite-2.1.4' into ignite-2.1.4

commit e9139d4916a22acab22008663e89f963f3d3a6b5
Author: sboikov 
Date:   2017-08-02T14:25:31Z

Call updateRebalanceVersion after evictions (was broken in 
c6fbe2d82a9f56f96c94551b09e85a12d192f32e);

(cherry picked from commit b277682)

commit 615a582b83d9acdd5703995f52f97e70027e0639
Author: Dmitriy Shabalin 
Date:   2017-08-21T12:34:59Z

IGNITE-4728 Fixed get params for saved state.
(cherry picked from commit 97b3cef)

commit 891a9e0001bd0d77e0bafc3ad109d04d02a9b7ff
Author: sboikov 
Date:   2017-08-21T10:21:44Z

ignite-6124 Merge exchanges for multiple discovery events

(cherry picked from commit bebf299799712b464ee0e3800752ecc07770d9f0)

commit 96d86acdfe1a251758c6915b473ceb20514cbbad
Author: sboikov 
Date:   2017-08-21T13:19:18Z

Merge remote-tracking branch 'community/ignite-2.1.4' into ignite-2.1.4

commit e9f729fcb9ba7b555aed246a834e385ce2c88795
Author: Alexey Goncharuk 
Date:   2017-08-21T10:49:22Z

ignite-5872 Replace standard java maps for partition counters with more 
effective data structures

(cherry picked from commit 918c409)

commit 8e672d4a83cb20136d375818505cacccf6c9b4fd
Author: sboikov 
Date:   2017-08-21T13:39:29Z

Changed ignite version.

commit fd5d83c44624baea9466c591f119195cb092df4c
Author: Alexey 

[GitHub] ignite pull request #2808: IGNITE-5224: .NET: PadLeft and PadRight support i...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2808


---

[jira] [Created] (IGNITE-6569) DROP table is frozen in special case

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-6569:
-

 Summary: DROP table is frozen in special case
 Key: IGNITE-6569
 URL: https://issues.apache.org/jira/browse/IGNITE-6569
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.1
Reporter: Vasiliy Sisko


In attached project file:
# Run node with using of DropFrozenTableStartup class.
Execution is frozen in time of DROP table process.



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

[GitHub] ignite pull request #2813: IGNITE-6272: .NET: Propagate multiple services de...

[apopovgg]

GitHub user apopovgg opened a pull request:

https://github.com/apache/ignite/pull/2813

IGNITE-6272: .NET: Propagate multiple services deployment

The following changes were made:
1. Java code:
added new JNI methods wrappers to Java: package 
org.apache.ignite.internal.processors.platform.services.PlatformServices with 
corresponding constants.
2. Net:
updated Apache.Ignite.Core.Services.IServices interface with new methods 
DeployAll() and DeployAllAsync()
added methods implementations
moved ServiceConfiguration serialization logic from 
Services.WriteServiceConfiguration() to ServiceConfiguration.Serialize()
updated Apache.Ignite.Core.Tests.Services tests with new ones
3. Executed & verified unit tests locally, TC is in progress

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-6272

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2813.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2813


commit 50c18578c6706d43b5561e2ba873c1c62bce0bca
Author: apopov 
Date:   2017-10-06T09:01:21Z

IGNITE-6272: .NET: Propagate multiple services deployment




---

[GitHub] ignite pull request #2751: ignite-5714-8

[voipp]

Github user voipp closed the pull request at:

https://github.com/apache/ignite/pull/2751


---

Re: Context switching for pessimistic transactions

[Dmitriy Setrakyan]

Thanks, Alexey.

I doubt anyone in the community will be able to answer your question here.
I am assuming that thread ID is not going to be enough to identify a
transaction, given that suspend happens in one thread, and resume in
another. However, to tell for sure would require a better understanding of
the code internals.

Perhaps it is best to summarize your thoughts in the ticket, before you
start the implementation. If no one in the community has any feedback, then
you can take a first crack at the code and submit a pull request.

D.


On Mon, Oct 2, 2017 at 3:49 PM, ALEKSEY KUZNETSOV 
wrote:

> Hi, Igntrs!
>
> I’m working on a ticket "Context switching for pessimistic transactions"
> [1].
>
> Goal of the ticket is to support transaction suspend()\resume() operations
> for pessimistic transactions. Resume can be called in another thread.
>
> Imagine, we started pessimistic transaction in thread T1 and then perform
> put operation, which leads to sending GridDistributedLockRequest to another
> node. Lock request contains thread id of the transaction. Then we call
> suspend, resume in another thread and we also must send messages to other
> nodes to change thread id.
>
> It seems complicated task.It’s better to get rid of sending thread id to
> the nodes.
>
> We can use transaction xid on other nodes instead of thread id. Xid is sent
> to nodes in GridDistributedLockRequest#nearXidVer
>
> So I propose:
>
> 1) On remote nodes instead of thread id of near transaction
> GridDistributedLockRequest#threadId use its xid
> GridDistributedLockRequest#nearXidVer.
>
> 2) Remove usages of near transaction's thread id on remote nodes.
>
> Thoughts?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-5714
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

[GitHub] ignite pull request #2751: ignite-5714-8

[voipp]

GitHub user voipp reopened a pull request:

https://github.com/apache/ignite/pull/2751

ignite-5714-8



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/voipp/ignite 
ignite-5714-local-lock-not-covered

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2751.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2751


commit 6f2f339adf78ccde554321f57041d74c6a75b10d
Author: voipp 
Date:   2017-09-26T13:08:05Z

Adding lock if timeout is negative

commit 94428f350e36485f6554134a7dab4f3db30d47f8
Author: voipp 
Date:   2017-10-06T08:05:36Z

Revert: Adding lock if timeout is negative

commit 3215f638cfaffe7d3c4466a2f8528ff969d53594
Author: voipp 
Date:   2017-10-06T08:06:15Z

exception when check lock owner




---

[jira] [Created] (IGNITE-6568) Failed to DROP table created by DDL query after restart

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-6568:
-

 Summary: Failed to DROP table created by DDL query after restart
 Key: IGNITE-6568
 URL: https://issues.apache.org/jira/browse/IGNITE-6568
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.1
Reporter: Vasiliy Sisko


In attached project:
# Run node by using of CreateTableStartup class.
# Stop node.
# Run node by using of DropTableStartup class.
On try to stop cache showed next exception:
{code}
Exception in thread "main" class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Unexpected DLL 
operation failure: class org.apache.ignite.IgniteCheckedException: Only cache 
created with CREATE TABLE may be removed with DROP TABLE 
[cacheName=SQL_PUBLIC_CITY]
at 
org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:280)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1385)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1923)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1919)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2401)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1927)
at startup.DropTableStartup.main(DropTableStartup.java:21)
Caused by: javax.cache.CacheException: class 
org.apache.ignite.IgniteCheckedException: Only cache created with CREATE TABLE 
may be removed with DROP TABLE [cacheName=SQL_PUBLIC_CITY]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1327)
at 
org.apache.ignite.internal.IgniteKernal.destroyCache0(IgniteKernal.java:3118)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.dynamicTableDrop(GridQueryProcessor.java:1436)
at 
org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:212)
... 7 more
Caused by: class org.apache.ignite.IgniteCheckedException: Only cache created 
with CREATE TABLE may be removed with DROP TABLE [cacheName=SQL_PUBLIC_CITY]
at 
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.processCacheChangeRequests(ClusterCachesInfo.java:628)
at 
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.onCacheChangeRequested(ClusterCachesInfo.java:392)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onCustomEvent(GridCacheProcessor.java:2927)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:664)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:564)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.notifyDiscoveryListener(ServerImpl.java:5461)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processCustomMessage(ServerImpl.java:5280)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2654)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2445)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6639)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2531)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{code}



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

Re: Monitoring of active transactions

[Sasha Belyak]

On Thu, Oct 5, 2017 at 1:24 PM, Alexey Goncharuk  wrote:

> Guys,
>
> I think we should not limit this functionality to http-rest only. We
should
> add this information to one of the MBeans as the primary information
> source. Then this should be added as a client command both to http-rest
and
> binary-rest endpoints, so the information is available through different
> tools.
>
> Thoughts?
Agree. Should we discuss command parameters here? For now txViewer handle 2
options:
1) time to decide that tx is "long", int in ms
2) server only flag to filter only tx's started from server, bool
I suggest it should handle:
1) time, int in ms
2) nodeType= {server,client,all}, all is default
3) show tx only or tx with keys, keys+values: entries={no,keys,entries} no
is default
maybe some filters, like:
4) nodes= to select tx only from specified nodes
5) txId= to select entries only by specified tx
6) cache= to select only tx with entries in specified cache(s?)
7) some another filter options like tx isolation level/tx mode, can anybody
write use cases for it?

2017-10-05 21:24 GMT+07:00 Ilya Lantukh :

> On Thu, Oct 5, 2017 at 1:24 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.com
> > wrote:
>
> > Guys,
> >
> > I think we should not limit this functionality to http-rest only. We
> should
> > add this information to one of the MBeans as the primary information
> > source. Then this should be added as a client command both to http-rest
> and
> > binary-rest endpoints, so the information is available through different
> > tools.
> >
> > Thoughts?
>
> I agree with this approach.
>
> On Thu, Oct 5, 2017 at 1:24 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.com
> > wrote:
>
> > Guys,
> >
> > I think we should not limit this functionality to http-rest only. We
> should
> > add this information to one of the MBeans as the primary information
> > source. Then this should be added as a client command both to http-rest
> and
> > binary-rest endpoints, so the information is available through different
> > tools.
> >
> > Thoughts?
> >
> > 2017-09-28 13:35 GMT+03:00 Sasha Belyak :
> >
> > > It's very useful, but I often we need to get list of hang transaction
> > when
> > > exchange stopped by some reason and in this case utility, based on
> client
> > > node won't help. I rewrite it as ComputeTask with default constructor,
> > add
> > > jar into ignite libs, activate http rest api and now it can be used
> from
> > > console and no need to update cluster topology:
> > >
> > > curl '
> > > http://127.0.0.1:8080/ignite?cmd=exe=org.apache.ignite.txviewer.
> > > RestCollectTxInfoTask=false=100
> > > '
> > >
> > > {"successStatus":0,"sessionToken":null,"error":
> null,"response":{"id":"~
> > > 98391a83-3d76-4e5e-b0c3-185cf2bd4acd","finished":true,
> > > "error":null,"result":[{"nearXidVersion":"GridCacheVersion
> > > [topVer=118063514, order=1506583525449,
> > > nodeOrder=2]","nodeId":"baa0237e-707c-4b69-abb6-
> > > 555a2fc17762","nodeString":"TcpDiscoveryNode
> > > [id=baa0237e-707c-4b69-abb6-555a2fc17762, addrs=[0:0:0:0:0:0:0:1%1,
> > > 10.0.3.1, 10.38.176.253, 10.42.1.107, 127.0.0.1, 172.17.0.1],
> > sockAddrs=[/
> > > 127.0.0.1:0, /10.42.1.107:0, /0:0:0:0:0:0:0:1%1:0, /172.17.0.1:0, /
> > > 10.38.176.253:0, /10.0.3.1:0], discPort=0, order=2, intOrder=0,
> > > lastExchangeTime=1506583525683, loc=true, ver=2.1.5#20170922-sha1:
> > > 6452201d,
> > > isClient=true]","threadId":1,"startTime":"Thu Sep 28 14:25:27 NOVT
> > > 2017","entries":[{"cache":"txCache","key":"1","value":"1"
> > > ,"operation":"CREATE"}]}]}}
> > >
> > > Even better if this tool can use binary rest too. I mean that we should
> > be
> > > able to run this collecting task from:
> > > 1) http rest api by curl/wget (but must deploy class somehow before, by
> > > peerClassLoad with Continues mode or by adding it to application
> > classpash)
> > > Good for admin's console scripting.
> > > 2) binary rest api by some java tool (with instant peerClassLoading).
> > Good
> > > for investigation on any grid configuration.
> > > 3) maybe, by client node as it implemented now (can't see any
> adwantages)
> > >
> > >
> > > 2017-09-16 5:35 GMT+07:00 Dmitry Pavlov :
> > >
> > > > Hi Ilya,
> > > >
> > > > I can help with including this utility into build/release, I've
> recenty
> > > > finished same steps for PDS WAL analysing tool for converting records
> > to
> > > > human readable format.
> > > > Please feel free to contact me.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > пт, 15 сент. 2017 г. в 6:37, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >:
> > > >
> > > > > It seems that the community (including me) really would like to see
> > > this
> > > > > feature in Ignite.
> > > > >
> > > > > Ilya, can you create a ticket and submit it for review?
> > > > >
> > > > > D.
> > > > >
> > > > > On Fri, Sep 8, 2017 at 7:15 AM, Anton Vinogradov 
> > >