date:20170811

Re: Cluster auto activation design proposal

2017-08-11 Thread Sergey Chugunov

More options to name the concept (one may put "node set" or "topology" at
the end - for me these are interchangeable):


   1. essential
   2. basic
   3. completed
   4. prepared
   5. solid
   6. enduring

To me the name must stress the fact that "node set" or "topology" contains
all nodes user is going to work with for a long run.
It is what user plans to work with and base the work on.

Any thoughts on this?

Thanks,
Sergey.

On Thu, Aug 10, 2017 at 5:41 PM, Sergey Chugunov 
wrote:

> Going down "node set" road:
>
> -fixed node set
> -established node set
> -base node set
>
> On Thu, Aug 10, 2017 at 5:23 PM, Dmitriy Setrakyan 
> wrote:
>
>> Can we brainstorm on the names again, I am not sure we have a consensus on
>> the name "baseline topology". This will be included in Ignite
>> configuration, so the name has to be clear.
>>
>> Some of the proposals were:
>>
>> - baseline topology
>> - minimal node set
>> - node restart set
>> - minimal topology
>>
>> Any other suggestions?
>>
>> D.
>>
>> On Thu, Aug 10, 2017 at 2:13 AM, Alexey Goncharuk <
>> alexey.goncha...@gmail.com> wrote:
>>
>> > Denis,
>> >
>> > This should be handled by the BT triggers. If I have 3 backups
>> configured,
>> > I actually won't care if my cluster will live 6 hours without an
>> additional
>> > backup. If for a partition there is only one backup left - a new BT
>> should
>> > be triggered automatically.
>> >
>> > 2017-08-10 0:33 GMT+03:00 Denis Magda :
>> >
>> > > Sergey,
>> > >
>> > > That’s the only concern I have:
>> > >
>> > > * 5. User takes out nodes from cluster (e.g. for maintenance
>> purposes):
>> > no
>> > >   rebalance happens until user recreates BLT on new cluster topology.*
>> > >
>> > > What if a node is crashed (or some other kind of outage) in the
>> middle of
>> > > the night and the user has to be sure that survived nodes will
>> rearrange
>> > > and rebalancing partitions?
>> > >
>> > > —
>> > > Denis
>> > >
>> > >
>> > > > On Aug 4, 2017, at 9:21 AM, Sergey Chugunov <
>> sergey.chugu...@gmail.com
>> > >
>> > > wrote:
>> > > >
>> > > > Folks,
>> > > >
>> > > > I've summarized all results from our discussion so far on wiki page:
>> > > > https://cwiki.apache.org/confluence/display/IGNITE/
>> > > Automatic+activation+design+-+draft
>> > > >
>> > > > I hope I reflected the most important details and going to add API
>> > > > suggestions for all use cases soon.
>> > > >
>> > > > Feel free to give feedback here or in comments under the page.
>> > > >
>> > > > Thanks,
>> > > > Sergey.
>> > > >
>> > > > On Thu, Aug 3, 2017 at 5:40 PM, Alexey Kuznetsov <
>> > akuznet...@apache.org>
>> > > > wrote:
>> > > >
>> > > >> Hi,
>> > > >>
>> > >  1. User creates new BLT using WebConsole or other tool and
>> "applies"
>> > > it
>> > > >> to brand-new cluster.
>> > > >>
>> > > >> Good idea, but we also should implement *command-line utility* for
>> the
>> > > same
>> > > >> use case.
>> > > >>
>> > > >> --
>> > > >> Alexey Kuznetsov
>> > > >>
>> > >
>> > >
>> >
>>
>
>

Re: Data compression in Ignite

2017-08-11 Thread Yakov Zhdanov

Ivan, your points definitely make sense, however, I see at list one issue
compared to per-page approach. With per-page we can split page to
compressed and uncompressed regions and change the dictionary if more
efficient compression is possible. With bigger areas such as partition or
entire cache dynamic dictionary change may be very complex.

--Yakov

Re: IgniteUtils#currentTimeMillis

2017-08-11 Thread Yakov Zhdanov

Well, then let's leave it as is for now.

--Yakov

[GitHub] ignite pull request #2433: Ignite 1.7.4 p3

2017-08-11 Thread ntikhonov

GitHub user ntikhonov opened a pull request:

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

Ignite 1.7.4 p3



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

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

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

https://github.com/apache/ignite/pull/2433.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 #2433


commit f24969f7e908645444df622642967a5f7fd3db23
Author: Evgenii Zhuravlev 
Date:   2017-07-19T16:30:07Z

IGNITE 5775 JobsProcessor fix bug with delay in compute

commit e7252f17ede973a76242b83c983c2730c62ff0c0
Author: nikolay_tikhonov 
Date:   2017-08-11T11:02:53Z

Fixed "IGNITE-5722 Cache entries stay in onheap after scan query execution 
for OFFHEAP_TIRED cache with expiry policy" (cherry picked from commit 37535634)

Signed-off-by: nikolay_tikhonov 

commit c55c34e27da9e5667ca1e8941a3d8c773e106258
Author: Evgenii Zhuravlev 
Date:   2017-08-01T14:46:27Z

IGNITE-5775 Fix removing jobs from activeJobs for jobAlwaysActivate (cherry 
picked from commit 8c992fb)

Signed-off-by: nikolay_tikhonov 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Design proposal: automatic creation of BaselineTopology

2017-08-11 Thread Sergey Chugunov

Folks,

As we are getting to the conclusion on the discussion about cluster
automatic activation proposal [1] I would like to propose one more thing
that may also be useful here.

In addition to options of creating BLT (BTW, any ideas of a better name for
the concept are welcome; feel free to send a message to [1]) on first
cluster activation or preparing it with UI tools user will be allowed to
prepare a descriptor of desired BLT and provide it through java API or
configuration file.

Workflow is as follows:


   1. User specifies a descriptor for desired baseline topology.
   E.g. API like this may be used: Ignite.activation().
   setBaselineTopologyDescriptor(BaselineTopologyDescriptor descriptor).

   2. Descriptor contains list of IP addressed (address ranges) and ports
   where cluster nodes are expected to start.
   List may be continuous or may contain excludes.

   3. As this descriptor may be large and is used only once through a
   lifetime of the cluster I suggest to provide it either through java API or
   in a separate file but not in a regular configuration file.

   4. Descriptor may be set to a cluster of even one node; after being set,
   it will verify topology on event from each node joined the cluster and
   activate cluster/create BLT automatically when desired topology reached.

   5. When cluster already has a BLT in metastore, any descriptors from API
   calls or files are ignored.


This feature will also provide us a way to notify user when some unexpected
nodes are joining the cluster.
E.g. we may define a separate event and fire it each time when node
unexpected by topology descriptor joins the cluster.

Thoughts?


[1] http://apache-ignite-developers.2346864.n4.nabble.com/
Cluster-auto-activation-design-proposal-tt20295.html

Thanks,
Sergey.

[GitHub] ignite pull request #2427: Ignite 4756

2017-08-11 Thread vadopolski

Github user vadopolski closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2434: IGNITE-6009: Fixed IgniteSemaphore test.

2017-08-11 Thread andrey-kuznetsov

GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-6009: Fixed IgniteSemaphore test.



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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6009

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

https://github.com/apache/ignite/pull/2434.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 #2434


commit 0aa7cc63a58ae2699c225d99b5b147ee50c7
Author: Andrey Kuznetsov 
Date:   2017-08-11T12:51:31Z

IGNITE-6009: Fixed IgniteSemaphore test.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2435: Ignite 4756

2017-08-11 Thread vadopolski

GitHub user vadopolski opened a pull request:

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

Ignite 4756

Added printDistribution method and AbstractAffinityFunctionSelfTest.

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

$ git pull https://github.com/vadopolski/ignite ignite-4756-2

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

https://github.com/apache/ignite/pull/2435.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 #2435


commit 30f3ae561459d3c04a06d647202f98ef9c4ef153
Author: vopolski <2w3e4r5t>
Date:   2017-07-04T13:30:26Z

IGNITE-4756

commit be797dbb474552080f1a33a56be799c2851528af
Author: vopolski <2w3e4r5t>
Date:   2017-07-04T13:38:50Z

IGNITE-4756

commit cc345de82c3c83b96500be537aa80499c09af7f0
Author: vopolski <2w3e4r5t>
Date:   2017-07-04T13:48:49Z

IGNITE-4756

commit f4212b5435fe8c1f27ca76223a8d4a9cc413831a
Author: vopolski <2w3e4r5t>
Date:   2017-07-04T16:10:13Z

IGNITE-4756

commit dc2b935bef44ab20a9c8b14d00d8ddf2bebddfa1
Author: vopolski <2w3e4r5t>
Date:   2017-07-05T09:33:24Z

IGNITE-4756

commit 56a65eab1c5e2a3d7671a6766bd28d477c4ffe7f
Author: vopolski <2w3e4r5t>
Date:   2017-07-05T12:00:51Z

IGNITE-4756

commit 1903cafc0b044771a2c111e24eb542f50d337c69
Author: vopolski <2w3e4r5t>
Date:   2017-07-06T14:37:44Z

IGNITE-4756

commit 7551f13a13ff720cc1d53cfeaf7c98a476d49118
Author: vopolski <2w3e4r5t>
Date:   2017-07-07T12:57:38Z

IGNITE-4756

commit b303fb5085ded69a4911c77a20f6ca32b64f0439
Author: vopolski <2w3e4r5t>
Date:   2017-07-10T09:33:15Z

IGNITE-4756

commit c9d6a33e5d14c90d8cf830f4764172f4dff41039
Author: vopolski <2w3e4r5t>
Date:   2017-07-10T14:32:48Z

IGNITE-4756

commit 0d6ab3cec30a970051ee06af3ffa6a15f3c455e5
Author: vopolski <2w3e4r5t>
Date:   2017-07-11T09:15:25Z

IGNITE-4756

commit 08fbdcbda4554cdc2e4641ce4076cbef29ebb1b1
Author: vopolski <2w3e4r5t>
Date:   2017-07-11T14:07:53Z

IGNITE-4756

commit 4d31cfb0c8235ed663cb913b166ab75818a739a2
Author: vopolski <2w3e4r5t>
Date:   2017-07-19T13:45:33Z

IGNITE-4756

commit 2a0d0955d35ab7f8647389066ebac259e4c51783
Author: vopolski <2w3e4r5t>
Date:   2017-07-20T14:03:30Z

IGNITE-4756
Improved Java Doc and Code Style.

commit 96cba61b3c266c67aa78829fc1b75ca0334bcff8
Author: vopolski <2w3e4r5t>
Date:   2017-07-20T14:35:55Z

IGNITE-4756
Improved Java Doc, Code Style and Abbreviation.

commit 8985596bacd745d266b296e11a9789839a11ee76
Author: vopolski <2w3e4r5t>
Date:   2017-07-21T11:46:17Z

IGNITE-4756
Improved Java Doc, Code Style and Abbreviation.

commit 5402fa02bb0befde402e290e38d5b711bdb7fc87
Author: vopolski <2w3e4r5t>
Date:   2017-07-24T11:48:11Z

deleted setter getter constructor

commit 4fe1ba1c8c1db507865f79a4ab4d37248d2608b6
Author: Max Kozlov 
Date:   2017-07-24T11:59:17Z

Merge branch 'ignite-4756' of https://github.com/vadopolski/ignite into 
vadim/ignite-4756

commit a208694bf76bf56e368cd68d045f4f13aad0e69a
Author: vopolski <2w3e4r5t>
Date:   2017-07-24T14:37:39Z

IGNITE-4756

commit 6cf30c9389c16d4a5ee53a0b0c7f9e2777555a8d
Author: vopolski <2w3e4r5t>
Date:   2017-07-24T14:56:30Z

IGNITE-4756

commit c15f7a8ed6f0c9696087396eca5cd934e62c8b07
Author: vopolski <2w3e4r5t>
Date:   2017-07-24T16:25:08Z

IGNITE-4756

commit 45830807563458da6e13b404e54c050294359ae3
Author: vopolski <2w3e4r5t>
Date:   2017-07-24T17:04:56Z

IGNITE-4756

commit 995075864f70d3aa8644482242edbbf472b71004
Author: vopolski <2w3e4r5t>
Date:   2017-07-24T17:19:52Z

IGNITE-4756

commit b05d959e899b8fe2237dada5d7aacdfaa1182166
Author: vopolski <2w3e4r5t>
Date:   2017-07-25T16:19:55Z

IGNITE-4756

commit 413889d67da6fa6e351d87ed930d4d64998e4c31
Author: vopolski <2w3e4r5t>
Date:   2017-07-25T16:25:32Z

IGNITE-4756

commit ebcfda10f50b77e6df2130521726e2bcceb8348e
Author: vopolski <2w3e4r5t>
Date:   2017-07-25T17:01:32Z

IGNITE-4756

commit 4d0b3621a6a089a482717b9d8351750cea817711
Author: vopolski <2w3e4r5t>
Date:   2017-07-27T12:07:33Z

IGNITE-4756

commit e0f0b12b7b64fc425513a8a74ad09fb1ff0b0360
Author: vopolski <2w3e4r5t>
Date:   2017-07-27T12:15:01Z

IGNITE-4756

commit 7fcd1acd586366a9c54b9145a365bb58ca186b80
Author: vopolski <2w3e4r5t>
Date:   2017-07-28T09:50:02Z

IGNITE-4756

commit d66512cee1eb6b2eb5fe91dd7bb3d558029109f0
Author: vopolski <2w3e4r5t>
Date:   2017-07-28T09:59:56Z

IGNITE-4756




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: IGNITE-5714 Context switching for pessimistic transactions

2017-08-11 Thread ALEKSEY KUZNETSOV

Hi!
There is GridCacheTxFinishSync synchronizer, which used to notify threads
(waiting on GridCacheTxFinishSync.TxFinishSync#pendingFut)
that GridNearTxFinishResponse is received.

Currently, only GridCacheTxFinishSync uses the synchronizer(but doesn't
wait on it somehow). And it seems the synchronizer is useless. Do we really
need to keep GridCacheTxFinishSync in a project?



ср, 9 авг. 2017 г. в 17:13, ALEKSEY KUZNETSOV :

> Hi, Igntrs!
>
> Currently we have context switching implemented for optimistic
> transactions : https://issues.apache.org/jira/browse/IGNITE-5712.
>
>
>
> So, the next step is to implement it for pessimistic transactions :
> https://issues.apache.org/jira/browse/IGNITE-5714
>
>
>
> The problem with them lies in *IgniteTxAdapter#threadId*. Thread id is
> transferred between nodes by GridDistributedTxPrepareRequest when key is
> got locked.
>
> When we suspend and resume transaction, thread id is got changed locally,
> but not on remote nodes.
>
>
>
> After studying the code, it seemed we can eliminate thread id from
> transactions completely.
>
> For that reason, i want to start implementing additional tests, that will
> cover transaction logic. Tickets would be created for them.
> Later on I will provide test scenarious and send you. *Will appreciate
> any ideas from you on new tests, thanks!*
>
>
>
> It will be the first step. The next one will be refactoring and
> eliminating thread id. What do you think ?
>
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>
-- 

*Best Regards,*

*Kuznetsov Aleksey*

Ignite: configuration changes at runtime

2017-08-11 Thread Yakov Zhdanov

Hello Igniters!

I want to start a discussion on a pretty useful feature that will help us
to bring Ignite's usability to the next level. How about supporting changes
to (some) configuration at runtime? Currently, most of the config props are
carved in stone and will require node restart for a change.

On this page I tried to summarize the vision and put the most important
properties (from my perspective) that will be handy to change at runtime:
https://cwiki.apache.org/confluence/display/IGNITE/Allow+Configuration+Settings+Change+At+Runtime

Alex Goncharuk, can you please help to fill in the suggestions for
persistence and memory config?

After we agree on properties list then I will file a ticket to implement
mechanism for properties propagation (via custom event or via ordinary
communication) and tickets for each Ignite's configuration bean and SPIs.

Comments are welcome.

--Yakov

Re: Ignite: configuration changes at runtime

2017-08-11 Thread Alexey Kuznetsov

Yakov,

Very cool feature.

I would also add to CacheConfiguration:
 StatisticsEnabled: on / off
 QueryDetailMetricsSize: change size

Please also implement an API that could be used from UI tools (Web Console
and Visor Cmd).


On Fri, Aug 11, 2017 at 10:49 PM, Yakov Zhdanov  wrote:

> Hello Igniters!
>
> I want to start a discussion on a pretty useful feature that will help us
> to bring Ignite's usability to the next level. How about supporting changes
> to (some) configuration at runtime? Currently, most of the config props are
> carved in stone and will require node restart for a change.
>
> On this page I tried to summarize the vision and put the most important
> properties (from my perspective) that will be handy to change at runtime:
> https://cwiki.apache.org/confluence/display/IGNITE/
> Allow+Configuration+Settings+Change+At+Runtime
>
> Alex Goncharuk, can you please help to fill in the suggestions for
> persistence and memory config?
>
> After we agree on properties list then I will file a ticket to implement
> mechanism for properties propagation (via custom event or via ordinary
> communication) and tickets for each Ignite's configuration bean and SPIs.
>
> Comments are welcome.
>
> --Yakov
>



-- 
Alexey Kuznetsov

[jira] [Created] (IGNITE-6044) SQL insert waits for transaction commit, but it must be executed right away

2017-08-11 Thread Mikhail Cherkasov (JIRA)

Mikhail Cherkasov created IGNITE-6044:
-

 Summary: SQL insert waits for transaction commit, but it must be 
executed right away
 Key: IGNITE-6044
 URL: https://issues.apache.org/jira/browse/IGNITE-6044
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.1
 Environment: Doc says:

""Presently, DML supports the atomic mode only meaning that if there is a DML 
query that is executed as a part of an Ignite transaction then it will not be 
enlisted in the transaction's writing queue and will be executed right away.""

https://apacheignite.readme.io/docs/dml#section-transactional-support

However the data will be added to cache only after transaction commit.
Reporter: Mikhail Cherkasov






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

Re: [jira] [Commented] (IGNITE-6026) init cluster for Ignite Persistence by xml

2017-08-11 Thread Alexey Kukushkin

Hi Alex,

Please specify "--port 11211" port when running "control.sh --activate". Also, 
add --host IGNITE_NODE if you run control.sh on a host where there are no 
ignite nodes. For example:

./bin/control.sh --host 127.0.0.1 --port 11211 --activate

It looks we have an issue that default Ignite command port is 11211 but 
control.sh uses 11212 by default.

Let me know if it did not help.

Best regards, Alexey


On Friday, August 11, 2017, 10:36:08 AM GMT+3, Alex Negashev (JIRA) 
 wrote:


    [ 
https://issues.apache.org/jira/browse/IGNITE-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122971#comment-16122971
 ] 

Alex Negashev commented on IGNITE-6026:
---

Hello Alexey, we add client to cluster with config:

        
        http://www.springframework.org/schema/beans"; 
xmlns:cache="http://www.springframework.org/schema/cache"; 
xmlns:context="http://www.springframework.org/schema/context"; 
xmlns:mvc="http://www.springframework.org/schema/mvc"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="      
  http://www.springframework.org/schema/beans         
http://www.springframework.org/schema/beans/spring-beans.xsd         
http://www.springframework.org/schema/cache         
http://www.springframework.org/schema/cache/spring-cache-3.1.xsd         
http://www.springframework.org/schema/context         
http://www.springframework.org/schema/context/spring-context.xsd ">
          
              
              
              
              
                
                    
                
              

              
              
                  
              
              
                
                    
                      
                          
                          
                          
                          
                      
                    
                
              
          
        


some logs from instances:
ignite-cache-client-5 | [07:29:53] Topology snapshot [ver=30, servers=5, 
clients=5, CPUs=40, heap=10.0GB]
ignite-cache-client-3 | [07:29:53] Topology snapshot [ver=30, servers=5, 
clients=5, CPUs=40, heap=10.0GB]
ignite-cache-client-2 | [07:29:53] Topology snapshot [ver=30, servers=5, 
clients=5, CPUs=40, heap=10.0GB]

but if i start script `./bin/control.sh --activate` it output: 
root@36ff2f004f78:/opt/ignite/apache-ignite-fabric-2.1.0-bin# ./bin/control.sh 
--activate
Aug 11, 2017 7:33:59 AM org.apache.ignite.internal.client.impl.GridClientImpl 

WARNING: Failed to initialize topology on client start. Will retry in 
background.
Aug 11, 2017 7:33:59 AM org.apache.ignite.internal.client.impl.GridClientImpl 

INFO: Client started [id=6b6279f1-6d5c-46a4-b88a-83d1378d94d2, protocol=TCP]
Something fail during activation, exception message: Latest topology update 
failed.
Aug 11, 2017 7:33:59 AM org.apache.ignite.internal.client.impl.GridClientImpl 
stop
INFO: Client stopped [id=6b6279f1-6d5c-46a4-b88a-83d1378d94d2, 
waitCompletion=true]


> init cluster for Ignite Persistence by xml 
> ---
>
>                Key: IGNITE-6026
>                URL: https://issues.apache.org/jira/browse/IGNITE-6026
>            Project: Ignite
>          Issue Type: Wish
>          Components: cache, examples, persistence
>    Affects Versions: 2.1
>        Environment: ignite in docker with zk
>            Reporter: Alex Negashev
>              Labels: documentation
>
> Hello! We use Ignite 2.1 and would like to use Ignite Persistence, how i can 
> do this without java code? xml only.
> Example attached.



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

Re: new website tickets

2017-08-11 Thread Akmal Chaudhri

Dimitriy,

I will take a look at those and pick-up the documentation tickets early
next week.

Thanks.

On 11 August 2017 at 02:34, Dmitriy Setrakyan  wrote:

> Igniters,
>
> I have filed several website tickets to reflect the addition of persistence
> in the latest 2.1 release:
>
> https://issues.apache.org/jira/browse/IGNITE-6036
> https://issues.apache.org/jira/browse/IGNITE-6037
> https://issues.apache.org/jira/browse/IGNITE-6038
> https://issues.apache.org/jira/browse/IGNITE-6039
> https://issues.apache.org/jira/browse/IGNITE-6039
> https://issues.apache.org/jira/browse/IGNITE-6040
> https://issues.apache.org/jira/browse/IGNITE-6041
>
> The idea behind this ticket to to improve user experience, documentation
> and feature descriptions. If anyone can think of more changes or additions,
> please reply in this thread.
>
> Denis, given your natural affinity and love towards the website changes
> (pun intended) I have assigned all of them to you, but feel free to
> unassign yourself.
>
> D.
>

Re: new website tickets

2017-08-11 Thread Dmitriy Setrakyan

On Fri, Aug 11, 2017 at 10:38 AM, Akmal Chaudhri <
akmal.chaud...@gridgain.com> wrote:

> Dimitriy,
>
> I will take a look at those and pick-up the documentation tickets early
> next week.
>
>
Awesome! Feel free to assign any tickets to yourself.


> Thanks.
>
> On 11 August 2017 at 02:34, Dmitriy Setrakyan 
> wrote:
>
> > Igniters,
> >
> > I have filed several website tickets to reflect the addition of
> persistence
> > in the latest 2.1 release:
> >
> > https://issues.apache.org/jira/browse/IGNITE-6036
> > https://issues.apache.org/jira/browse/IGNITE-6037
> > https://issues.apache.org/jira/browse/IGNITE-6038
> > https://issues.apache.org/jira/browse/IGNITE-6039
> > https://issues.apache.org/jira/browse/IGNITE-6039
> > https://issues.apache.org/jira/browse/IGNITE-6040
> > https://issues.apache.org/jira/browse/IGNITE-6041
> >
> > The idea behind this ticket to to improve user experience, documentation
> > and feature descriptions. If anyone can think of more changes or
> additions,
> > please reply in this thread.
> >
> > Denis, given your natural affinity and love towards the website changes
> > (pun intended) I have assigned all of them to you, but feel free to
> > unassign yourself.
> >
> > D.
> >
>

Re: SQL Getting Started Guide

2017-08-11 Thread Akmal Chaudhri

Denis, All

I have made some progress with the documentation:

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  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
>
> Please share your thoughts in JIRA or in this discussion.
>
> Akmal, who perfected his technical writer skills working for IBM,
> volunteered to take over this task. Akmal, please create an account in
> Ignite JIRA and share it with us. You’ll be able to assign the task on
> yourself afterwards.
> https://issues.apache.org/jira/projects/IGNITE
>
> Moreover, once the guide is ready Prachi will use it as a basis for the
> new SQL screencast we need to produce.
>
> —
> Denis
>

Re: Ignite: configuration changes at runtime

2017-08-11 Thread Dmitriy Setrakyan

Yakov,

I like the idea, but I am not sure how we will separate properties that are
dynamically changeable from the constant ones.

Also, what is the API for updating these properties? Perhaps we can create
a special interface, e.g. IgniteConfigurationRuntime (similar to Java
Runtime class), which will have only setters and have all the properties
that can be changed at runtime.

D.

On Fri, Aug 11, 2017 at 8:49 AM, Yakov Zhdanov  wrote:

> Hello Igniters!
>
> I want to start a discussion on a pretty useful feature that will help us
> to bring Ignite's usability to the next level. How about supporting changes
> to (some) configuration at runtime? Currently, most of the config props are
> carved in stone and will require node restart for a change.
>
> On this page I tried to summarize the vision and put the most important
> properties (from my perspective) that will be handy to change at runtime:
> https://cwiki.apache.org/confluence/display/IGNITE/
> Allow+Configuration+Settings+Change+At+Runtime
>
> Alex Goncharuk, can you please help to fill in the suggestions for
> persistence and memory config?
>
> After we agree on properties list then I will file a ticket to implement
> mechanism for properties propagation (via custom event or via ordinary
> communication) and tickets for each Ignite's configuration bean and SPIs.
>
> Comments are welcome.
>
> --Yakov
>

Re: Hibernate dialect for Ignite

2017-08-11 Thread Valentin Kulichenko

I think that's a great idea. Although I doubt anyone aver tried to use
Ignite with Hibernate this way, so we need to do some testing first to
identify limitations/issues we have there.

-Val

On Wed, Aug 9, 2017 at 12:58 PM, Dmitriy Setrakyan 
wrote:

> Igniters,
>
> Given that we have a very rich SQL support starting with version 2.1, does
> it make sense to create an Ignite SQL dialect for Hibernate?
>
> https://docs.jboss.org/hibernate/orm/3.6/reference/en-US/html/session-
> configuration.html#configuration-optional-dialects
>
> D.
>

Invitation: GoToWebinar - Introduction to Apache Ignite, a memory-cen... @ Wed Aug 16, 2017 12am - 1am (PDT) (dev@ignite.apache.org)

2017-08-11 Thread dmagda

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20170816T07Z
DTEND:20170816T08Z
DTSTAMP:20170811T182601Z
ORGANIZER;CN=dma...@gridgain.com:mailto:dma...@gridgain.com
UID:4rdsf1dkkdm1ngn5h0qeq25...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=dma...@gridgain.com;X-NUM-GUESTS=0:mailto:dma...@gridgain.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@ignite.apache.org;X-NUM-GUESTS=0:mailto:dev@ignite.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=u...@ignite.apache.org;X-NUM-GUESTS=0:mailto:u...@ignite.apache.org
CREATED:20170811T182601Z
DESCRIPTION:Igniters\,\n\nJoin Akmal Chaudhri's webinar and learn about the
  many components of Apache Ignite\, including the Data Grid\, Compute Grid\
 , distributed SQL database and the Machine Learning Grid. We will also cove
 r a few typical use cases and work through some Java code examples.\n\nREGI
 STRATION LINK: https://register.gotowebinar.com/register/242331631530346624
 1 \n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~::~:~::-\nPlease do not edit this section of the description.\n\n
 This event has a Google Hangouts video call.\nJoin: https://plus.google.com
 /hangouts/_/gridgain.com/gotowebinar?hceid=ZG1hZ2RhQGdyaWRnYWluLmNvbQ.4rdsf
 1dkkdm1ngn5h0qeq25ac1&hs=121\n\nView your event at https://www.google.com/c
 alendar/event?action=VIEW&eid=NHJkc2YxZGtrZG0xbmduNWgwcWVxMjVhYzEgZGV2QGlnb
 ml0ZS5hcGFjaGUub3Jn&tok=MTkjZG1hZ2RhQGdyaWRnYWluLmNvbTllMmFiMTE3YTE3ZWUwNGR
 mNDA4ZmFmM2Q5YTQ4MDIzNDQ0MGY0MDU&ctz=America/Los_Angeles&hl=en.\n-::~:~::~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~:
 :-
LAST-MODIFIED:20170811T182601Z
LOCATION:GoToWebinar - See conference call information below
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:GoToWebinar - Introduction to Apache Ignite\, a memory-centric dist
 ributed platform
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics

Updated Invitation: GoToWebinar - Introduction to Apache Ignite, a memory-cen... @ Wed Aug 16, 2017 12am - 1am (PDT) (dev@ignite.apache.org)

2017-08-11 Thread dmagda

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20170816T07Z
DTEND:20170816T08Z
DTSTAMP:20170811T182806Z
ORGANIZER;CN=dma...@gridgain.com:mailto:dma...@gridgain.com
UID:4rdsf1dkkdm1ngn5h0qeq25...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=dma...@gridgain.com;X-NUM-GUESTS=0:mailto:dma...@gridgain.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@ignite.apache.org;X-NUM-GUESTS=0:mailto:dev@ignite.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=u...@ignite.apache.org;X-NUM-GUESTS=0:mailto:u...@ignite.apache.org
CREATED:20170811T182601Z
DESCRIPTION:Igniters\,\n\nJoin Akmal Chaudhri's webinar and learn about the
  many components of Apache Ignite\, including the Data Grid\, Compute Grid\
 , distributed SQL database and the Machine Learning Grid. We will also cove
 r a few typical use cases and work through some Java code examples.\n\nREGI
 STRATION LINK: https://register.gotowebinar.com/register/242331631530346624
 1 \n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~::~:~::-\nPlease do not edit this section of the description.\n\n
 View your event at https://www.google.com/calendar/event?action=VIEW&eid=NH
 Jkc2YxZGtrZG0xbmduNWgwcWVxMjVhYzEgZGV2QGlnbml0ZS5hcGFjaGUub3Jn&tok=MTkjZG1h
 Z2RhQGdyaWRnYWluLmNvbTllMmFiMTE3YTE3ZWUwNGRmNDA4ZmFmM2Q5YTQ4MDIzNDQ0MGY0MDU
 &ctz=America/Los_Angeles&hl=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20170811T182806Z
LOCATION:GoToWebinar - See conference call information below
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:GoToWebinar - Introduction to Apache Ignite\, a memory-centric dist
 ributed platform
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics

[jira] [Created] (IGNITE-6045) Hibernate dialect for Ignite

2017-08-11 Thread Dmitriy Setrakyan (JIRA)

Dmitriy Setrakyan created IGNITE-6045:
-

 Summary: Hibernate dialect for Ignite
 Key: IGNITE-6045
 URL: https://issues.apache.org/jira/browse/IGNITE-6045
 Project: Ignite
  Issue Type: Wish
  Components: hibernate, sql
Reporter: Dmitriy Setrakyan


Given that we have a very rich SQL support starting with version 2.1, it makes 
sense to create an Ignite SQL dialect for Hibernate?

https://docs.jboss.org/hibernate/orm/3.6/reference/en-US/html/session-configuration.html#configuration-optional-dialects



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

Re: Hibernate dialect for Ignite

2017-08-11 Thread Dmitriy Setrakyan

I filed a ticket: https://issues.apache.org/jira/browse/IGNITE-6045

Maybe someone in the community will pick it up.

D.

On Fri, Aug 11, 2017 at 11:14 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> I think that's a great idea. Although I doubt anyone aver tried to use
> Ignite with Hibernate this way, so we need to do some testing first to
> identify limitations/issues we have there.
>
> -Val
>
> On Wed, Aug 9, 2017 at 12:58 PM, Dmitriy Setrakyan 
> wrote:
>
> > Igniters,
> >
> > Given that we have a very rich SQL support starting with version 2.1,
> does
> > it make sense to create an Ignite SQL dialect for Hibernate?
> >
> > https://docs.jboss.org/hibernate/orm/3.6/reference/en-US/html/session-
> > configuration.html#configuration-optional-dialects
> >
> > D.
> >
>

Re: new website tickets

2017-08-11 Thread Denis Magda

Akmal,

Thanks for stepping in! Considering that you’ve been working on the SQL getting 
started, I’ve reassigned the general getting guide task on you and provide more 
details and suggestions for it:
https://issues.apache.org/jira/browse/IGNITE-6041 


Please let me know if you have any questions.

I’ll take care of the rest.

—
Denis

> On Aug 11, 2017, at 10:40 AM, Dmitriy Setrakyan  wrote:
> 
> On Fri, Aug 11, 2017 at 10:38 AM, Akmal Chaudhri <
> akmal.chaud...@gridgain.com> wrote:
> 
>> Dimitriy,
>> 
>> I will take a look at those and pick-up the documentation tickets early
>> next week.
>> 
>> 
> Awesome! Feel free to assign any tickets to yourself.
> 
> 
>> Thanks.
>> 
>> On 11 August 2017 at 02:34, Dmitriy Setrakyan 
>> wrote:
>> 
>>> Igniters,
>>> 
>>> I have filed several website tickets to reflect the addition of
>> persistence
>>> in the latest 2.1 release:
>>> 
>>> https://issues.apache.org/jira/browse/IGNITE-6036
>>> https://issues.apache.org/jira/browse/IGNITE-6037
>>> https://issues.apache.org/jira/browse/IGNITE-6038
>>> https://issues.apache.org/jira/browse/IGNITE-6039
>>> https://issues.apache.org/jira/browse/IGNITE-6039
>>> https://issues.apache.org/jira/browse/IGNITE-6040
>>> https://issues.apache.org/jira/browse/IGNITE-6041
>>> 
>>> The idea behind this ticket to to improve user experience, documentation
>>> and feature descriptions. If anyone can think of more changes or
>> additions,
>>> please reply in this thread.
>>> 
>>> Denis, given your natural affinity and love towards the website changes
>>> (pun intended) I have assigned all of them to you, but feel free to
>>> unassign yourself.
>>> 
>>> D.
>>> 
>>

Ignite integrations

2017-08-11 Thread Dmitriy Setrakyan

Igniters,

I have reviewed the Ignite integrations page, and it looks like most
integrations are stuck on 1.9 version:

https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations

We should upgrade them to the latest release.

Andrey Gura, can you please comment?

D.

Re: SQL Getting Started Guide

2017-08-11 Thread Denis Magda

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  
> wrote:
> 
> Denis, All
> 
> I have made some progress with the documentation:
> 
> 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  > 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 
> 
> 
> Please share your thoughts in JIRA or in this discussion.
> 
> Akmal, who perfected his technical writer skills working for IBM, volunteered 
> to take over this task. Akmal, please create an account in Ignite JIRA and 
> share it with us. You’ll be able to assign the task on yourself afterwards.
> https://issues.apache.org/jira/projects/IGNITE 
> 
> 
> Moreover, once the guide is ready Prachi will use it as a basis for the new 
> SQL screencast we need to produce.
> 
> —
> Denis
>

[jira] [Created] (IGNITE-6046) Multiple SQL statements in one command do not work

2017-08-11 Thread Dmitriy Setrakyan (JIRA)

Dmitriy Setrakyan created IGNITE-6046:
-

 Summary: Multiple SQL statements in one command do not work
 Key: IGNITE-6046
 URL: https://issues.apache.org/jira/browse/IGNITE-6046
 Project: Ignite
  Issue Type: Bug
  Components: jdbc
Reporter: Dmitriy Setrakyan
Assignee: Vladimir Ozerov
Priority: Blocker
 Fix For: 2.2


I have connected to Ignite from DBeaver using our thin JDBC driver. When I 
execute more than one statement from the SQL Editor, I get an error.

For example, highlighting and executing these 2 statements gives an error:
{code:sql}
INSERT INTO city (id, name) VALUES (2, 'Forest Hill');
INSERT INTO person (id, name, city_id) VALUES (2, 'John Doe', 3);
{code}
Here is the error I get:
{code}
[15:25:17,265][SEVERE][sql-connector-#150%null%][JdbcRequestHandler] Failed to 
execute SQL query [reqId=26, req=JdbcQueryExecuteRequest [schemaName=null, 
pageSize=1024, maxRows=0, sqlQry=INSERT INTO city (id, name) VALUES (2, 'Forest 
Hill');
INSERT INTO person (id, name, city_id) VALUES (2, 'John Doe', 3), args=[]]]
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Can 
not set org.h2.command.Prepared field org.h2.command.CommandContainer.prepared 
to org.h2.command.CommandList
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1863)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:188)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:122)
at 
org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:152)
at 
org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:44)
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)
Caused by: class org.apache.ignite.IgniteCheckedException: Can not set 
org.h2.command.Prepared field org.h2.command.CommandContainer.prepared to 
org.h2.command.CommandList
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2316)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1860)
... 12 more
Caused by: java.lang.IllegalArgumentException: Can not set 
org.h2.command.Prepared field org.h2.command.CommandContainer.prepared to 
org.h2.command.CommandList
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167)
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171)
at 
sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:58)
at 
sun.reflect.UnsafeObjectFieldAccessorImpl.get(UnsafeObjectFieldAccessorImpl.java:36)
at java.lang.reflect.Field.get(Field.java:393)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser$Getter.get(GridSqlQueryParser.java:1600)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.prepared(GridSqlQueryParser.java:443)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1298)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1856)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1852)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2293)
... 13 more
{code}




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

[jira] [Created] (IGNITE-6047) Need to support "show" SQL commands

2017-08-11 Thread Dmitriy Setrakyan (JIRA)

Dmitriy Setrakyan created IGNITE-6047:
-

 Summary: Need to support "show" SQL commands
 Key: IGNITE-6047
 URL: https://issues.apache.org/jira/browse/IGNITE-6047
 Project: Ignite
  Issue Type: Bug
  Components: jdbc, sql
Reporter: Dmitriy Setrakyan
Assignee: Vladimir Ozerov
Priority: Blocker
 Fix For: 2.2


I have connected to Ignite from DBeaver using our thin JDBC driver. When I 
execute "show" commands, I get an error. 

We need to support all or most {{SHOW}} commands in H2, as described here:
http://www.h2database.com/html/grammar.html?highlight=show&search=show#show

Also, ideally, if a user issues {{DESCRIBE}} or {{DESC}} commands, we should 
give a message to use the {{SHOW}} command, if possible.




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

[jira] [Created] (IGNITE-6048) Need to document how to connect to Ignite from external SQL tools

2017-08-11 Thread Dmitriy Setrakyan (JIRA)

Dmitriy Setrakyan created IGNITE-6048:
-

 Summary: Need to document how to connect to Ignite from external 
SQL tools
 Key: IGNITE-6048
 URL: https://issues.apache.org/jira/browse/IGNITE-6048
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Dmitriy Setrakyan
Assignee: Denis Magda
 Fix For: 2.2


We need to provide all the possible required JDBC and ODBC settings. We should 
also pick any SQL tool and provide screenshots. For example, DBeaver is a good 
candidate.

http://dbeaver.jkiss.org/

D.



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

SQL usability issues

2017-08-11 Thread Dmitriy Setrakyan

Igniters,

I have tried to connect to Ignite from DBeaver [1], and realized that there
are some usability issues we need to address before the next release:

   1. We need to have documentation on how to configure JDBC and ODBC
   drivers with external SQL tools [2]
   2. You cannot highlight multiple SQL statements and run them together [3]
   3. Commands like *DESCRIBE* or *SHOW* do not work [4]
   4. Schema, index, and table metadata is not displayed [5]. Looks like
   this fix was already implemented.

The links to the tickets are below.

[1] http://dbeaver.jkiss.org/
[2] https://issues.apache.org/jira/browse/IGNITE-6048
[3] https://issues.apache.org/jira/browse/IGNITE-6046
[4] https://issues.apache.org/jira/browse/IGNITE-6047
[5] https://issues.apache.org/jira/browse/IGNITE-5233

D.

Re: Design proposal: automatic creation of BaselineTopology

2017-08-11 Thread Dmitriy Setrakyan

I would call the setter setBaselineTopology, without the word Descriptor.

Also, perhaps this BaselineTopology should be a standard predicate, just
like the Node Filter we already have for ClusterGroup, so users could
provide a custom cluster initialization logic. We, of course, should
provide a default implementation of this predicate, which accepts a list of
IP addresses or host names.

Thoughts?

D.

On Fri, Aug 11, 2017 at 4:47 AM, Sergey Chugunov 
wrote:

> Folks,
>
> As we are getting to the conclusion on the discussion about cluster
> automatic activation proposal [1] I would like to propose one more thing
> that may also be useful here.
>
> In addition to options of creating BLT (BTW, any ideas of a better name for
> the concept are welcome; feel free to send a message to [1]) on first
> cluster activation or preparing it with UI tools user will be allowed to
> prepare a descriptor of desired BLT and provide it through java API or
> configuration file.
>
> Workflow is as follows:
>
>
>1. User specifies a descriptor for desired baseline topology.
>E.g. API like this may be used: Ignite.activation().
>setBaselineTopologyDescriptor(BaselineTopologyDescriptor descriptor).
>
>2. Descriptor contains list of IP addressed (address ranges) and ports
>where cluster nodes are expected to start.
>List may be continuous or may contain excludes.
>
>3. As this descriptor may be large and is used only once through a
>lifetime of the cluster I suggest to provide it either through java API
> or
>in a separate file but not in a regular configuration file.
>
>4. Descriptor may be set to a cluster of even one node; after being set,
>it will verify topology on event from each node joined the cluster and
>activate cluster/create BLT automatically when desired topology reached.
>
>5. When cluster already has a BLT in metastore, any descriptors from API
>calls or files are ignored.
>
>
> This feature will also provide us a way to notify user when some unexpected
> nodes are joining the cluster.
> E.g. we may define a separate event and fire it each time when node
> unexpected by topology descriptor joins the cluster.
>
> Thoughts?
>
>
> [1] http://apache-ignite-developers.2346864.n4.nabble.com/
> Cluster-auto-activation-design-proposal-tt20295.html
>
> Thanks,
> Sergey.
>

Re: Cluster auto activation design proposal

2017-08-11 Thread Dmitriy Setrakyan

Sergey,

As it is becoming clear from another thread, the only configuration users
will need to provide is the initial set of nodes. Everything else will be
handled by Ignite automatically.

In this case, the name Baseline Topology will appear only in documentation,
in which case the name is OK (that is if I am understanding the design
correctly).

However, the list initial set of nodes can be called initialActivationNodes.

Makes sense?

D.

On Fri, Aug 11, 2017 at 2:46 AM, Sergey Chugunov 
wrote:

> More options to name the concept (one may put "node set" or "topology" at
> the end - for me these are interchangeable):
>
>
>1. essential
>2. basic
>3. completed
>4. prepared
>5. solid
>6. enduring
>
> To me the name must stress the fact that "node set" or "topology" contains
> all nodes user is going to work with for a long run.
> It is what user plans to work with and base the work on.
>
> Any thoughts on this?
>
> Thanks,
> Sergey.
>
> On Thu, Aug 10, 2017 at 5:41 PM, Sergey Chugunov <
> sergey.chugu...@gmail.com>
> wrote:
>
> > Going down "node set" road:
> >
> > -fixed node set
> > -established node set
> > -base node set
> >
> > On Thu, Aug 10, 2017 at 5:23 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> >> Can we brainstorm on the names again, I am not sure we have a consensus
> on
> >> the name "baseline topology". This will be included in Ignite
> >> configuration, so the name has to be clear.
> >>
> >> Some of the proposals were:
> >>
> >> - baseline topology
> >> - minimal node set
> >> - node restart set
> >> - minimal topology
> >>
> >> Any other suggestions?
> >>
> >> D.
> >>
> >> On Thu, Aug 10, 2017 at 2:13 AM, Alexey Goncharuk <
> >> alexey.goncha...@gmail.com> wrote:
> >>
> >> > Denis,
> >> >
> >> > This should be handled by the BT triggers. If I have 3 backups
> >> configured,
> >> > I actually won't care if my cluster will live 6 hours without an
> >> additional
> >> > backup. If for a partition there is only one backup left - a new BT
> >> should
> >> > be triggered automatically.
> >> >
> >> > 2017-08-10 0:33 GMT+03:00 Denis Magda :
> >> >
> >> > > Sergey,
> >> > >
> >> > > That’s the only concern I have:
> >> > >
> >> > > * 5. User takes out nodes from cluster (e.g. for maintenance
> >> purposes):
> >> > no
> >> > >   rebalance happens until user recreates BLT on new cluster
> topology.*
> >> > >
> >> > > What if a node is crashed (or some other kind of outage) in the
> >> middle of
> >> > > the night and the user has to be sure that survived nodes will
> >> rearrange
> >> > > and rebalancing partitions?
> >> > >
> >> > > —
> >> > > Denis
> >> > >
> >> > >
> >> > > > On Aug 4, 2017, at 9:21 AM, Sergey Chugunov <
> >> sergey.chugu...@gmail.com
> >> > >
> >> > > wrote:
> >> > > >
> >> > > > Folks,
> >> > > >
> >> > > > I've summarized all results from our discussion so far on wiki
> page:
> >> > > > https://cwiki.apache.org/confluence/display/IGNITE/
> >> > > Automatic+activation+design+-+draft
> >> > > >
> >> > > > I hope I reflected the most important details and going to add API
> >> > > > suggestions for all use cases soon.
> >> > > >
> >> > > > Feel free to give feedback here or in comments under the page.
> >> > > >
> >> > > > Thanks,
> >> > > > Sergey.
> >> > > >
> >> > > > On Thu, Aug 3, 2017 at 5:40 PM, Alexey Kuznetsov <
> >> > akuznet...@apache.org>
> >> > > > wrote:
> >> > > >
> >> > > >> Hi,
> >> > > >>
> >> > >  1. User creates new BLT using WebConsole or other tool and
> >> "applies"
> >> > > it
> >> > > >> to brand-new cluster.
> >> > > >>
> >> > > >> Good idea, but we also should implement *command-line utility*
> for
> >> the
> >> > > same
> >> > > >> use case.
> >> > > >>
> >> > > >> --
> >> > > >> Alexey Kuznetsov
> >> > > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
>

Re: Data compression in Ignite

2017-08-11 Thread Dmitriy Setrakyan

I still don't understand per-partition compression, which is only local.
How do entries get updated in the middle of a partition file?

D.

On Fri, Aug 11, 2017 at 3:44 AM, Yakov Zhdanov  wrote:

> Ivan, your points definitely make sense, however, I see at list one issue
> compared to per-page approach. With per-page we can split page to
> compressed and uncompressed regions and change the dictionary if more
> efficient compression is possible. With bigger areas such as partition or
> entire cache dynamic dictionary change may be very complex.
>
> --Yakov
>

Re: SQL usability issues

2017-08-11 Thread Denis Magda

Dmitriy,

That's the documentation that shows how to configure Pentaho via JDBC:
https://apacheignite-tools.readme.io/v2.1/docs/pentaho

Plus on the tools' domain you can see Tableau based ODBC example.

So, I'm not sure we need something else from the documentation standpoint.
I would rather add a direct reference from JDBC/ODBC docs to Pentaho and
Tablea.

Denis

On Friday, August 11, 2017, Dmitriy Setrakyan  wrote:

> Igniters,
>
> I have tried to connect to Ignite from DBeaver [1], and realized that there
> are some usability issues we need to address before the next release:
>
>1. We need to have documentation on how to configure JDBC and ODBC
>drivers with external SQL tools [2]
>2. You cannot highlight multiple SQL statements and run them together
> [3]
>3. Commands like *DESCRIBE* or *SHOW* do not work [4]
>4. Schema, index, and table metadata is not displayed [5]. Looks like
>this fix was already implemented.
>
> The links to the tickets are below.
>
> [1] http://dbeaver.jkiss.org/
> [2] https://issues.apache.org/jira/browse/IGNITE-6048
> [3] https://issues.apache.org/jira/browse/IGNITE-6046
> [4] https://issues.apache.org/jira/browse/IGNITE-6047
> [5] https://issues.apache.org/jira/browse/IGNITE-5233
>
> D.
>

Re: Cluster auto activation design proposal

Re: Data compression in Ignite

Re: IgniteUtils#currentTimeMillis

[GitHub] ignite pull request #2433: Ignite 1.7.4 p3

Design proposal: automatic creation of BaselineTopology

[GitHub] ignite pull request #2427: Ignite 4756

[GitHub] ignite pull request #2434: IGNITE-6009: Fixed IgniteSemaphore test.

[GitHub] ignite pull request #2435: Ignite 4756

Re: IGNITE-5714 Context switching for pessimistic transactions

Ignite: configuration changes at runtime

Re: Ignite: configuration changes at runtime

[jira] [Created] (IGNITE-6044) SQL insert waits for transaction commit, but it must be executed right away

Re: [jira] [Commented] (IGNITE-6026) init cluster for Ignite Persistence by xml

Re: new website tickets

Re: new website tickets

Re: SQL Getting Started Guide

Re: Ignite: configuration changes at runtime

Re: Hibernate dialect for Ignite

Invitation: GoToWebinar - Introduction to Apache Ignite, a memory-cen... @ Wed Aug 16, 2017 12am - 1am (PDT) (dev@ignite.apache.org)

Updated Invitation: GoToWebinar - Introduction to Apache Ignite, a memory-cen... @ Wed Aug 16, 2017 12am - 1am (PDT) (dev@ignite.apache.org)

[jira] [Created] (IGNITE-6045) Hibernate dialect for Ignite

Re: Hibernate dialect for Ignite

Re: new website tickets

Ignite integrations

Re: SQL Getting Started Guide

[jira] [Created] (IGNITE-6046) Multiple SQL statements in one command do not work

[jira] [Created] (IGNITE-6047) Need to support "show" SQL commands

[jira] [Created] (IGNITE-6048) Need to document how to connect to Ignite from external SQL tools

SQL usability issues

Re: Design proposal: automatic creation of BaselineTopology

Re: Cluster auto activation design proposal

Re: Data compression in Ignite

Re: SQL usability issues

33 matches

Site Navigation

Mail list logo

Footer information