[ 
https://issues.apache.org/jira/browse/CAMEL-13261?focusedWorklogId=231457&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-231457
 ]

ASF GitHub Bot logged work on CAMEL-13261:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Apr/19 15:27
            Start Date: 23/Apr/19 15:27
    Worklog Time Spent: 10m 
      Work Description: DenisIstomin commented on pull request #2880: 
CAMEL-13261: Fix consumer configuration, speed up tests run
URL: https://github.com/apache/camel/pull/2880
 
 
   1. Fixed consumer configuration bug
   1. Speeded up tests run
   1. Increaseed DB pool size (only for unit-tests)
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 231457)
    Time Spent: 8.5h  (was: 8h 20m)

> jooq - Create XML DSL API for using database as shared queue
> ------------------------------------------------------------
>
>                 Key: CAMEL-13261
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13261
>             Project: Camel
>          Issue Type: Sub-task
>            Reporter: Denis Istomin
>            Assignee: Denis Istomin
>            Priority: Major
>             Fix For: 3.0.0, 3.0.0-M2
>
>          Time Spent: 8.5h
>  Remaining Estimate: 0h
>
> Database table could be used as a queue, where Producer writes data, Consumer 
> reads data (with deletion or not).
> Hibernate component has support of it:
> |{{consumeDelete}}|{{true}}|Option for HibernateConsumer only. Specifies 
> whether or not the entity is deleted after it is consumed.|
> [http://camel.apache.org/hibernate.html]
> Need to improve XML DSL API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to