Hi Igniters!
I'm currently working on the ODBC driver [1] and I'd wish to add
documentation for it somewhere. Is readme.io [2] appropriate
place for that? If so can I get edit permissions to modify it? If not
can you point out the right place for the ODBC documentation?
[1] -
Igniters,
The latest blogs were added to the Ignite website news section:
https://ignite.apache.org/
https://ignite.apache.org/news.html
Thanks to Roman Shtykh and Shamim Bhuiyan for contributing.
Blogs about Ignite go a long way towards improving adoption and awareness
about our project. I
Valentin Kulichenko created IGNITE-2786:
---
Summary: SpringCache doesn't survive client reconnect
Key: IGNITE-2786
URL: https://issues.apache.org/jira/browse/IGNITE-2786
Project: Ignite
Roman Shtykh created IGNITE-2788:
Summary: Redis API for Ignite to work with data via the Redis
protocol
Key: IGNITE-2788
URL: https://issues.apache.org/jira/browse/IGNITE-2788
Project: Ignite
Hi guys, I am quite busy now. It looks like I'll just start implementing
PersistenceCallback in a month.
--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7827.html
Sent from the Apache Ignite Developers mailing list
Valentin Kulichenko created IGNITE-2787:
---
Summary: Hibernate L2 cache doesn't survive client reconnect
Key: IGNITE-2787
URL: https://issues.apache.org/jira/browse/IGNITE-2787
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/539
---
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
Valentin Kulichenko created IGNITE-2785:
---
Summary: Improve test coverage for web session clustering
Key: IGNITE-2785
URL: https://issues.apache.org/jira/browse/IGNITE-2785
Project: Ignite
I think we should document it in readme, right next to JDBC driver:
https://apacheignite.readme.io/docs/jdbc-driver
I would probably create a category called “Drivers”, and put JDBC and ODBC
drivers under it. Remember to copy this documentation to 1.6 as well.
D.
On Wed, Mar 9, 2016 at 9:37 AM,
Is there any way to get rid of this property completely?
On Wed, Mar 9, 2016 at 4:10 AM, Denis Magda wrote:
> Igniters,
>
> As you know there is a property that controls maximum remove queue history
> for atomic caches
>
Hello,
It's come to my attention, when registering the cache event listener, the
filters get deployed on all the nodes of the cache, despite the fact that the
cache is configured as REPLICATED. This seems redundant since it's sufficient
to have the filter deployed only on the node that has
Can I get edit permissions for readme?
Best Regards,
Igor
On Wed, Mar 9, 2016 at 10:25 PM, Dmitriy Setrakyan
wrote:
> I think we should document it in readme, right next to JDBC driver:
> https://apacheignite.readme.io/docs/jdbc-driver
>
> I would probably create a
Done.
On Wed, Mar 9, 2016 at 12:42 PM, Igor Sapego wrote:
> Can I get edit permissions for readme?
>
> Best Regards,
> Igor
>
> On Wed, Mar 9, 2016 at 10:25 PM, Dmitriy Setrakyan
> wrote:
>
> > I think we should document it in readme, right next to
Hello all,
I am working on IGNITE-2693 with Vlad Ozerov's help. I am somewhat of a
Java newbie so please be gentle ;-)
I am curious about something - after reading the Javadocs and Binary
Marshaller docs on Ignite's documentation websites, I think that the
documentation is not very friendly
Hi Andrey.
The replicated cache is just a partitioned cache with more backups. I think
the filter is deployed on all nodes, but is only invoked on the primary
node (correct me if I am wrong). In that case, it will be impossible to
deploy it only on the node that registered it.
D.
On Wed, Mar 9,
Andrey,
Are you talking about a continuous query or a distributed event listener?
On Wed, Mar 9, 2016 at 3:43 AM, 李玉珏@163 <18624049...@163.com> wrote:
> Hi:
>
> If I write the content will be released to:
> Https://www.zybuluo.com/liyuj/note/230739
Is your blog in Chinese? If yes, then I doubt we can help promote it.
However, I believe that you can post it to any developer
Alexey,
I'm talking about JCache's CacheEntry listener (which I think is implemented on
top of the continuous query feature).
Andrey
> Date: Wed, 9 Mar 2016 15:52:48 -0800
> Subject: Re: CacheEntryEventFilter with Replicated caches
> From: alexey.goncha...@gmail.com
> To: dev@ignite.apache.org
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/443
---
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
Hi:
If I write the content will be released to:
Https://www.zybuluo.com/liyuj/note/230739
I say "authority", mainly refers to the relevant content, if written by
the designer, will be more depth.
在 16/3/9 11:16, Dmitriy Setrakyan 写道:
On Thu, Mar 3, 2016 at 11:45 PM, 李玉珏@163
Vladimir Ozerov created IGNITE-2782:
---
Summary: Implement single NEAR ATOMIC update future.
Key: IGNITE-2782
URL: https://issues.apache.org/jira/browse/IGNITE-2782
Project: Ignite
Issue
Github user ilantukh closed the pull request at:
https://github.com/apache/ignite/pull/511
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/531
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/533
---
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
Vladimir Ozerov created IGNITE-2781:
---
Summary: IGFS: Automatically set "copyOnRead" to "false" for IGFS
caches.
Key: IGNITE-2781
URL: https://issues.apache.org/jira/browse/IGNITE-2781
Project:
Igniters,
As you know there is a property that controls maximum remove queue
history for atomic caches
(IgniteSystemProperties.IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE).
The strange thing is that this property is also used for transactional
caches as well. I see that GridDhtLocalPartition
Igor Sapego created IGNITE-2780:
---
Summary: CPP: Review Ignite C++ building process with Autotools.
Key: IGNITE-2780
URL: https://issues.apache.org/jira/browse/IGNITE-2780
Project: Ignite
Issue
Dmitriy,
The reason for my posting was exactly that: the filter is both deployed and
invoked on all nodes where the REPLICATED cache is started. My point is that
the filter should only be deployed and invoked on the node where its
corresponding listener is, namely the local node (the node that
On 3/9/2016 7:46 PM, Alexey Goncharuk wrote:
Note that withKeepBinary() is just a way to tell a cache not to deserialize
values when doing a get or running an entry processor. The concept of
binary object does not belong solely to caches - you can get an instance of
IgniteBinary interface from
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/523
---
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
GitHub user iveselovskiy opened a pull request:
https://github.com/apache/ignite/pull/540
Hunk perf 1119
DO NOT MERGE!
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iveselovskiy/ignite hunk-perf-1119
Alternatively you can
Noam Liran created IGNITE-2783:
--
Summary: Frequent deadlock during regular operations
Key: IGNITE-2783
URL: https://issues.apache.org/jira/browse/IGNITE-2783
Project: Ignite
Issue Type: Bug
Hi,
The current version of test is not very clean and it works only because
withKeepBinary() is a noop. The correct version would be to use plain cache
for non-binary-object entry processor and use withKeepBinary for
binary-object entry processor. You can see that EntryProcessor creation is
Alexey,
Thank you for the explanation!
But why any of that matters in this case? I'm talking about the REPLICATED
cache -- all data changes get applied to all nodes in the same order on all
nodes. And I'm talking about a cache event listener that is instantiated on one
of thise nodes. It can
Dmitriy is right, currently REPLICATED cache works the same way as
PARTITIONED does, and in PARTITIONED cache filters should be evaluated on
backups in order to maintain a backup queue in case a primary node fails.
For the case when query is executed on an affinity node of a REPLICATED
cache
On 3/9/2016 6:43 PM, Alexey Goncharuk wrote:
Hi,
The current version of test is not very clean and it works only because
withKeepBinary() is a noop. The correct version would be to use plain cache
for non-binary-object entry processor and use withKeepBinary for
binary-object entry processor.
Note that withKeepBinary() is just a way to tell a cache not to deserialize
values when doing a get or running an entry processor. The concept of
binary object does not belong solely to caches - you can get an instance of
IgniteBinary interface from Ignite and use binary objects in computations,
Alexey Goncharuk created IGNITE-2784:
Summary: Optimize continuous query remote listener invocation
Key: IGNITE-2784
URL: https://issues.apache.org/jira/browse/IGNITE-2784
Project: Ignite
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/541
IGNITE-2663: Added "Protocol Version" field to ODBC communication protocol.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite
Vladimir Ozerov created IGNITE-2779:
---
Summary: BinaryMarshaller caches must be cleaned during client
reconnect.
Key: IGNITE-2779
URL: https://issues.apache.org/jira/browse/IGNITE-2779
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/499
---
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
41 matches
Mail list logo