关于Liquibase近期是否计划支持Apache Ignite的技术问询

Hey there! Great question about pairing Liquibase with Apache Ignite for your microservices architecture's database proxy component. Let me share what I know about this:

• Current Official Status
  As of right now, Liquibase doesn’t offer official out-of-the-box support for Apache Ignite. Its official supported database list leans toward traditional relational systems and some popular NoSQL platforms, but Ignite isn’t included in that lineup yet.

• Near-Term Plans
  From what’s publicly available in Liquibase’s issue trackers and community discussions, there’s no announced timeline or active development initiative to add Apache Ignite support in the immediate future. That said, feature requests for Ignite have popped up from other users, so it’s possible it could be prioritized if there’s enough community demand.

• Workarounds to Explore
  If you need to move forward with your stack, here are a couple of options:

  • Try leveraging Liquibase’s generic JDBC support: Ignite offers a JDBC driver, so you could configure Liquibase to use this driver. Just note that you might hit limitations—some of Liquibase’s abstract change types (like createTable with specific constraints) might not translate perfectly, and you might need to fall back to writing raw SQL changes instead.
  • Build a custom Liquibase extension: Liquibase has a flexible extension API that lets you add support for new databases. This would require developing code to handle Ignite-specific logic for change tracking, validation, and execution, but it’s a viable path if generic JDBC doesn’t cut it.

If Ignite support is critical for your project, I’d suggest submitting a detailed feature request to the Liquibase team, making sure to highlight your microservices database proxy use case—specific, real-world use cases help the team prioritize new features. You could also engage with the Liquibase community to rally support from other users who might have similar needs.

内容的提问来源于stack exchange，提问作者user3755972