Hello, Looks reasonable. Also, it looks like the 'ignite-direct-io' module has redundant 'ignite-indexing' dependency too (perhaps it's required for tests, but dependency scope should be 'test' in this case). I will remove redundant 'ignite-indexing' dependencies from 'ignite-spring' and 'ignite-direct-io' modules next week, if there is no objection from anyone.
пт, 23 дек. 2022 г. в 03:39, 18624049226 <18624049...@163.com>: > Hiteam, > > Because Ignite3.0 is a new product and the community has developed a new > SQL engine, the situation has changed a lot. I think the community > should promote the merge of this simple patch, this wrong dependency may > cause new problems. > > 在 2022/12/23 08:32, 18624049226 写道: > > https://issues.apache.org/jira/browse/IGNITE-5713 > > > > 在 2022/12/23 00:09, mwiesenberg 写道: > >> Hi, > >> Is there any reason the ignite spring pom has ignite indexing as a > >> dependency? I was switching from h2 to calcite and observed h2 was by > >> default still being brought in via ignite spring, for seemingly no > >> reason. > >> > >> If there's no reason, I'm happy to submit an MR to remove, please > >> enable my > >> JIRA account, mberg, as a contributor. Thank you! > >> > >> Mike > >>
