Re: Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

} > ).size()); > > // Executed without exception but return no results. > > assertEquals(2, sql( > "SELECT IID FROM T1 WHERE ID IN (?) AND IID = ?", > new Object[] {Arrays.asList("1", "4").toArray(),

Re: Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

and SQL) that worked on 2.8 and start failing on 2.13. > > > This seems like a regression, was this intentional? > > Looks like a bug to me. > Details of your schema and query can help in further investigation. > > > 10 мая 2022 г., в 10:14, Courtney Robinson > написа

Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

Hi all, We're looking to do a major upgrade from 2.8.0 to 2.13.0 After the initial upgrade our test suite started failing (about 15% of tests now fail). No other change has been made other than the Ignite version number. org.apache.ignite.internal.processors.query.IgniteSQLException: General > er

Re: Ignite JOIN fails to return results using WHERE clause

gt; partitioned by "releaseId", T1 by "t0Id", and you make a join by columns > that aren't affinity columns (id = tableId). > > You should specify the flag "SqlFieldsQuery.setDistributedJoins(true)" to > make your join return correct results. > >

Ignite JOIN fails to return results using WHERE clause

I have a query like this: SELECT > tbl.id AS tbl_id, tbl.releaseId AS tbl_releaseId, col.type AS col_type > FROM T0 tbl > INNER JOIN T1 col ON tbl.id = col.tableId > *WHERE tbl.releaseId = ? AND tbl.name = ?* > LIMIT 100 > This returns no results so after investigating, I ended

Debugging long persistence recovery on restart

How can we find out what's causing Ignite to take an hour each on this cache? Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io

Virtual Ignite meetup - Building Hypi's lowcode BaaS on Ignite

me challenges and pitfalls to avoid. Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io

Re: Best practices on how to approach data centre aware affinity

replay changes from the application side effectively duplicating a part of what Ignite's doing. Did I miss anything and if not, how would you suggest handling this in the case of multiple clusters - one in each data centre? Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123

Re: Best practices on how to approach data centre aware affinity

e table name. So if a table is currently called A and we add a virtual catalog then we keep a mapping that says when the user wants to call "A" it should really go to table "A_v2" or something. This comes with its own challenge and a massive testing overhead. Regards, Courtney Robinson F

Best practices on how to approach data centre aware affinity

d you recommend implementing the affinity function to be aware of the data centre? 4. Are there any other caveats we need to be thinking about? There is a lot of existing data, we want to try to avoid a full copy/move to new tables if possible, that will prove to be very difficult in produ

Re: Reliably duplicate SQL cache

geKey, value_type=Page\"") > > Regards, > -- > Ilya Kasnacheev > > > сб, 13 февр. 2021 г. в 19:32, Courtney Robinson >: > >> Due to an issue I posted about in a previous thread >> http://apache-ignite-users.70518.x6.nabble.com/Basic-SQL-pagination

Reliably duplicate SQL cache

etValue()); } //strmr.flush(); } log.info("Total in target cache {}", to.sizeLong(CachePeekMode.ALL)); } } Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io

Re: Cannot create SQL index with INLINE_SIZE if ` is used

ackticks_id_k_v ON public.backticks (`id`, `k`, `v`) INLINE_SIZE 150; " ); } On Sat, Feb 6, 2021 at 2:38 PM Courtney Robinson wrote: > If you use >> >> CREATE INDEX IF NOT EXISTS myIdx ON myTbl(myCol) INLINE_SIZE 200; > > then this works as expected. If the column

Cannot create SQL index with INLINE_SIZE if ` is used

x27;ve found a workaround is to use " instead of ` > CREATE INDEX IF NOT EXISTS myIdx ON myTbl("myCol") INLINE_SIZE 200; First found in 2.8.1 and verified to still fail on 2.9.1. Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io

Re: Ignite in-memory + other SQL store without fully loading all data into Ignite

gn would have Ignite in front of anything we end up doing. We'll sort out the call details closer to the time. Thanks Denis, speak to you and Val in two weeks. Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https:/

Re: Ignite in-memory + other SQL store without fully loading all data into Ignite

We'd effectively be using Ignite in-memory to accelerate Greenplum and ES queries through a consistent SQL API whilst getting the benefits of the well established and battle tested Postgres tools and ecosystem...and SQL base ML. I'd appreciate your thoughts here on this around the sugges

Re: Ignite in-memory + other SQL store without fully loading all data into Ignite

I know this was over the holiday so bumping. Can anyone provide any pointers on where to start looking or anything else mentioned in the previous email? Thanks On Sat, Dec 26, 2020 at 8:39 PM Courtney Robinson wrote: > We've been using Ignite in production for almost 3 years and we

Ignite in-memory + other SQL store without fully loading all data into Ignite

pabilities and so we can't easily take this away. FYI it doesn't have to be CacheStore, I realise this just inherits the JCache interface just generally can something like CacheStore be implemented to replace the integration that Ignite persistence provides? Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io

Re: Why does CacheBasedDataSet destroy the cache it is given

is showed up in tests before it got anywhere near production data. In our case, we're push data into a cache continually and rebuilding the model periodically. Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io>

Re: Deploying Ignite in Docker

ss to bind to by setting > IgniteConfiguration#setLocalhost(). > > Thanks, > Pavel > > пн, 29 июн. 2020 г. в 21:18, Courtney Robinson >: > >> I've deployed Ignite bare-metal and in Kubernetes in test and production >> but I'm now trying to deploy for a n

Re: Deploying Ignite in Docker

Bumping this. Any suggestions on the below? Not only is it undesirable to run the cluster on public IPs from a security aspect but it incurs additional cost in the cloud env it is being deployed in. On Mon, Jun 29, 2020 at 7:18 PM Courtney Robinson wrote: > I've deployed Ignite bare-m

Re: SELECT values of each row within groups on a table with composite primary key

On Mon, Jul 6, 2020 at 9:42 AM Stephen Darlington < stephen.darling...@gridgain.com> wrote: > I’m not sure I understand the question. Can you give an example of the > source data and the results you’re expecting? > > On 4 Jul 2020, at 19:17, Courtney Robinson > wro

Deploying Ignite in Docker

10.131.53.147:47500 10.131.77.79:47500 10.131.60.224:47500 10.131.77.111:47500 10.131.77.93:47500 10.131.77.84:47500 Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io

Re: stddev* and var* etc are not implemented but are documented

te.apache.org%3E > > https://issues.apache.org/jira/browse/IGNITE-3180 > > Regards, > Stephen > > On 22 Jun 2020, at 10:16, Courtney Robinson > wrote: > > Hi, > The STDDEV* and VAR* SQL functions are documented on both Ignite and > GridGain websites but are not imple

stddev* and var* etc are not implemented but are documented

ed? Using Ignite 2.8. Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io

Why does CacheBasedDataSet destroy the cache it is given

er withFilter(IgniteBiPredicate filterToAdd) { return datasetBuilder.withFilter(filterToAdd); } }; which works but seems very hacky. Are we misusing the API somehow - examples/docs do not mention or indicate anything about this as far as I've found. Regards, Courtney Robinson Founder a

Re: Unable to enable ML inference storage

ignite.cluster().active(true) after ignite = IgnitionEx.start(cfg, springGridCtx) Regards, Courtney Robinson Founder and CEO, Hypi https://hypi.io On Thu, May 21, 2020 at 9:55 PM akorensh wrote: > Hi, > > Looks like you are loading the ML plugin twice (see below) > Can you try w/out the p

Re: Re: Backups not being done for SQL caches

Hi Alexandr, Thanks, I didn't know the metrics and topology info was different. I found the issue, we were not adding the nodes to the baseline topology due to a bug. We're using v2.8.0 in the upgrade/migration, previous version is 2.7 Regards, Courtney Robinson Founder and CEO, Hypi

Re: Backups not being done for SQL caches

^-- TxLog region [used=0MB] ^-- hypi region [used=3MB] ^-- Outbound messages queue [size=0] ^-- Public thread pool [active=0, idle=0, qSize=0] ^-- System thread pool [active=0, idle=6, qSize=0] Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <h

Backups not being done for SQL caches

ess(AbstractProtocol.java:860) >at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1587) >at > org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) >at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) >at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) >at > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) >at java.base/java.lang.Thread.run(Thread.java:834) > > Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> https://hypi.io

Re: SQL MERGE INTO with SELECT UNION

what motivated using merge in the first place since we'd incur parsing once and fewer network round trips...that was the theory anyway, we never got as far as benchmarking to know for sure with our workload because we never got the MERGE query working. Regards, Courtney Robinson Founder and CEO

SQL MERGE INTO with SELECT UNION

27;a','a','a' > SELECT ?,?,?,?,?,?,?,?,?,?,?,? > --SELECT ?,?,(IFNULL(SELECT hypi_created FROM hypi_store_App WHERE > hypi_instanceId = ? AND hypi_id = ?, CURRENT_TIMESTAMP())),?,?,?,?,?,?,?,?,? > ) [50004-197] > at org.h2.message.DbException.getJdbcSQLException(DbException.java:357) > at org.h2.message.DbException.get(DbException.java:179) > at org.h2.message.DbException.get(DbException.java:155) > at org.h2.value.Value.getHigherOrder(Value.java:370) > at org.h2.command.dml.SelectUnion.prepare(SelectUnion.java:348) > at org.h2.command.dml.Merge.prepare(Merge.java:283) > at org.h2.command.Parser.prepareCommand(Parser.java:283) > at org.h2.engine.Session.prepareLocal(Session.java:611) > at org.h2.engine.Session.prepareCommand(Session.java:549) > at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1247) > at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:76) > at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:694) > at > org.apache.ignite.internal.processors.query.h2.ConnectionManager.prepareStatementNoCache(ConnectionManager.java:363) > at > org.apache.ignite.internal.processors.query.h2.QueryParser.parseH2(QueryParser.java:345) > ... 24 common frames omitted > Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> https://hypi.io

Re: Transaction already completed errors

kets I can keep track of? Depending on time needed, we could potentially contribute to getting this released. Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io On Wed, Apr 15, 2020 at 3:26 PM Evgenii Zhura

Transaction already completed errors

CompletedCheckedException: Transaction is > already completed. at org.apache.ignite.internal.processors.cache.mvcc. > MvccUtils.checkActive(MvccUtils.java:684) at org.apache.ignite.internal. > processors.query.h2.IgniteH2Indexing.executeSelect(IgniteH2Indexing.java: > 1255) ... 26 common frames omitted > Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44 208 123 2413 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io

Re: Fulltext matching

pstream if it'll be accepted. Regards, Courtney Robinson CTO, Hypi Tel: +4402032870961 (GMT+0) <https://hypi.io> <https://hypi.io> https://hypi.io On Thu, Sep 6, 2018 at 4:09 PM Ilya Kasnacheev wrote: > Hello! > > Unfortunately, fulltext doesn't seem to h

Fulltext matching

Hi, We've got Ignite in production and decided to start using some fulltext matching as well. I've investigated and can't figure out why my queries are not matching. I construct a query entity e.g new QueryEntity(keyClass, valueClass) and in debug I can see it generates a list of fields e.g. a, b