Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2902
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2901
---
It looks like the case sensitivity for the affinity key is a bug. Vladimir,
what do you think?
On Mon, Oct 23, 2017 at 11:19 AM, Denis Magda wrote:
> Vladimir, thanks a lot for looking into this!
>
> > On Oct 23, 2017, at 12:35 AM, Vladimir Ozerov
> wrote:
> >
> > Denis,
> >
> > Now more detail
Igniters,
Some of our community members benchmarked regular SSDs vs Intel Optan (3d
XPoint). Here is a report:
http://dmagda.blogspot.com/2017/10/3d-xpoint-outperforms-ssds-verified-on.html
Please help to spread a word:
https://twitter.com/denismagda/status/922587654033518593
—
Denis
Hi,
If you can sacrifice Spark APIs in Python then use Ignite Python client like
that [1] or connect from ODBC [2] directly. Hope that IgniteRDD support will be
added for Python at some point on time but there are no any plans yet.
[1] https://github.com/dany74q/python-apache-ignite
[2] https:/
Prachi,
Thanks for creating the docs! Please leave your usability related feedback in
this ticket [1]. I changed it’s priority targeting for 2.4 release because
totally agree with you that presently the script doesn’t behave like a normal
tool (no help page, meaningless log, etc.).
[1] https:
Guys,
I have added the documentation for Cluster Activation -
https://apacheignite.readme.io/docs/cluster-activation
While documenting, I noticed that the message printed on executing the
"control.sh --activate|deactivate" command is not giving me any useful
information. I can't tell if the clust
Hey Vladimir,
Maybe it'd be better to just use JUL logger directly?
Or, better yet, just get rid of that nagging patronizing warning on line 434
(the only reason the logger is created in the first place) altogether and
instead optionally throw an IAE?
Or, include a dummy config/java.util.loggi
Vladimir, thanks a lot for looking into this!
> On Oct 23, 2017, at 12:35 AM, Vladimir Ozerov wrote:
>
> Denis,
>
> Now more detailed answer:
>
> 1) It is expected that "City" class is not be found. You should set
> key/value type names to fully-qualified class name to make it work.
> Improvem
Denis Magda created IGNITE-6717:
---
Summary: Hashcode/equals is not needed for custom keys serialized
into a binary form
Key: IGNITE-6717
URL: https://issues.apache.org/jira/browse/IGNITE-6717
Project: Ig
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2910
---
Nicholas DiPiazza created IGNITE-6716:
-
Summary: Document "Affinity key backups mismatch" resolution steps
Key: IGNITE-6716
URL: https://issues.apache.org/jira/browse/IGNITE-6716
Project: Ignite
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/2910
Ignite 6512
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6512
Alternatively you can review and apply these
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/2909
TCP communication skip local node loopback address
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6639
Alter
Hi Andrey,
What kind of fix do you suggest?
On Mon, Oct 23, 2017 at 6:58 PM, Andrey Kornev
wrote:
> Hello,
>
> Just curious if anyone knows why IgniteJdbcDriver class instantiates a
> JavaLogger() on line 410 rather than using the globally configured logger
> instance?
>
> I have an slf4j logge
Hello,
Just curious if anyone knows why IgniteJdbcDriver class instantiates a
JavaLogger() on line 410 rather than using the globally configured logger
instance?
I have an slf4j logger configured and with ignite-indexing module in the
classpath, I get scary looking (albeit benign) message in m
It looks like there is no way to access and IgniteRDD from a python
SparkContext.
Our use case is wanting to share rdd's between Python and Scala. Leveraging
the performance of Scala and the ds tools available in Python.
Are there any plans to implement this in the near future?
--
Sent from:
Pavel Tupitsyn created IGNITE-6715:
--
Summary: .NET:
DataStorageConfiguration.WalAutoArchiveAfterInactivity
Key: IGNITE-6715
URL: https://issues.apache.org/jira/browse/IGNITE-6715
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2880
---
Pavel Tupitsyn created IGNITE-6714:
--
Summary: .NET: IgniteConfiguration missing properties
Key: IGNITE-6714
URL: https://issues.apache.org/jira/browse/IGNITE-6714
Project: Ignite
Issue Type:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2907
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2865
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2772
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2817
---
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/2908
Added IgniteOOM propagation for client node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6654
Alternativel
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/2907
IGNITE-6713: Ignite Cache 5 flaky test
CacheRebalancingSelfTest.testDisableRebalancing()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridg
Dmitriy Pavlov created IGNITE-6713:
--
Summary: Ignite Cache 5 flaky test
CacheRebalancingSelfTest.testDisableRebalancing()
Key: IGNITE-6713
URL: https://issues.apache.org/jira/browse/IGNITE-6713
Proje
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/2906
IGNITE-6071 White list of exceptions to suppress in createTcpClient.
Also add wait in discovery infinite loop to avoid grind
You can merge this pull request into a Git repository by running:
$
Alexey Goncharuk created IGNITE-6712:
Summary: Add data volume metrics to data region metrics
Key: IGNITE-6712
URL: https://issues.apache.org/jira/browse/IGNITE-6712
Project: Ignite
Issue
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/2905
IGNITE-6071 White list of exceptions to suppress in createTcpClient.
Also add wait in discovery infinite loop to avoid grind
You can merge this pull request into a Git repository by running:
$
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/2904
IGNITE-6071 White list of exceptions to suppress in createTcpClient.
Also add wait in discovery infinite loop to avoid grind
You can merge this pull request into a Git repository by running:
$
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/2903
IGNITE-6071 White list of exceptions to suppress in createTcpClient.
Also add wait in discovery infinite loop to avoid grind
You can merge this pull request into a Git repository by running:
$
Alexey Goncharuk created IGNITE-6711:
Summary: DataRegionMetrics#totalAllocatedPages is not valid after
node restart
Key: IGNITE-6711
URL: https://issues.apache.org/jira/browse/IGNITE-6711
Project
Alexey Goncharuk created IGNITE-6710:
Summary: Add page replace age metric
Key: IGNITE-6710
URL: https://issues.apache.org/jira/browse/IGNITE-6710
Project: Ignite
Issue Type: Improvement
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2902
IGNITE-6708 Remove ignite-compatibility from optional directory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ign
Semen Boikov created IGNITE-6709:
Summary: Support mvcc filter for H2TreeIndex.findFirstOrLast
Key: IGNITE-6709
URL: https://issues.apache.org/jira/browse/IGNITE-6709
Project: Ignite
Issue Ty
Hi, Igntrs!
I would like to implement suspend\resume methods of a pessimistic
transaction as following:
if transaction holds lock on a key and suspend method has been called no
keys would be unlocked. Therefore,
if transaction holds lock on a key and suspend method has been called,
topology chan
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2901
IGNITE-6706 Remove ignite-sqlline module from optioanl directory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ig
Sergey Kozlov created IGNITE-6708:
-
Summary: Remove ignite-compatibility from optional directory
Key: IGNITE-6708
URL: https://issues.apache.org/jira/browse/IGNITE-6708
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-6707:
--
Summary: .NET: Machine learning APIs
Key: IGNITE-6707
URL: https://issues.apache.org/jira/browse/IGNITE-6707
Project: Ignite
Issue Type: Improvement
Sergey Kozlov created IGNITE-6706:
-
Summary: Remove ignite-sqlline module from optioanl directory
Key: IGNITE-6706
URL: https://issues.apache.org/jira/browse/IGNITE-6706
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-6705:
--
Summary: .NET: CacheConfiguration missing properties
Key: IGNITE-6705
URL: https://issues.apache.org/jira/browse/IGNITE-6705
Project: Ignite
Issue Type:
Pavel Tupitsyn created IGNITE-6704:
--
Summary: .NET: CacheConfiguration.KeyConfiguration
Key: IGNITE-6704
URL: https://issues.apache.org/jira/browse/IGNITE-6704
Project: Ignite
Issue Type: Im
Val,
When a bean is requested by type/class, which is how SpringResource
injection is done, Spring walks through all *bean definitions* and tries to
figure out a suitable bean by calling to getSingleton method and thus trying
to acquire exactly the same lock. So, any bean could be the reason of th
Semen Boikov created IGNITE-6703:
Summary: Unnecessary lookup in
BPlusTree.ForwardCursor.fillFromBuffer for startIdx 0
Key: IGNITE-6703
URL: https://issues.apache.org/jira/browse/IGNITE-6703
Project:
Semen Boikov created IGNITE-6702:
Summary: Get rid of values deserialization in
H2TreeIndex.getRowCount
Key: IGNITE-6702
URL: https://issues.apache.org/jira/browse/IGNITE-6702
Project: Ignite
Semen Boikov created IGNITE-6701:
Summary: Do not deserialize previous value during indexes update
Key: IGNITE-6701
URL: https://issues.apache.org/jira/browse/IGNITE-6701
Project: Ignite
Issu
Semen Boikov created IGNITE-6700:
Summary: Node considered as failed can cause failure of others
nodes
Key: IGNITE-6700
URL: https://issues.apache.org/jira/browse/IGNITE-6700
Project: Ignite
Vladimir Ozerov created IGNITE-6699:
---
Summary: Optimize client-side data streamer performance
Key: IGNITE-6699
URL: https://issues.apache.org/jira/browse/IGNITE-6699
Project: Ignite
Issue T
Denis,
Now more detailed answer:
1) It is expected that "City" class is not be found. You should set
key/value type names to fully-qualified class name to make it work.
Improvements: docs
2) There is no need to implement hash code. Why did you do this?
3) We will not have case-insensitive policy,
50 matches
Mail list logo
