Ingress subpaths of primary service to separate services

Kubernetes
1

Is it possible to do something like below with kong? Currently it appears that all requests go to the task service and /task/batch calls won’t actually follow the /task/batch path because they’re consumed by the higher level wildcard.

  rules:
  - host: www.task-doer.com
    http:
      paths:
        - path: /task*
          backend:
            serviceName: task-service
            servicePort: 80
        - path: /task/batch*
          backend:
            serviceName: task-batch-service
            servicePort: 80
2

You can split the rules into two different Ingress resources and then have different regex priorities for them to solve this.