You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Mark Webb (JIRA)" <ji...@apache.org> on 2012/10/09 21:52:03 UTC
[jira] [Created] (CAMEL-5696) camel-mongodb save operation should
put have configurable option to put WriteResult in header
Mark Webb created CAMEL-5696:
--------------------------------
Summary: camel-mongodb save operation should put have configurable option to put WriteResult in header
Key: CAMEL-5696
URL: https://issues.apache.org/jira/browse/CAMEL-5696
Project: Camel
Issue Type: Improvement
Components: camel-mongodb
Affects Versions: 2.10.1
Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
Reporter: Mark Webb
Priority: Minor
Fix For: 2.11.0
I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5696) camel-mongodb write operations
should put have configurable option to put WriteResult in header
Posted by "Mark Webb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476061#comment-13476061 ]
Mark Webb commented on CAMEL-5696:
----------------------------------
Sorry I did not see this in time. I did start working on a patch, but I will test yours instead. Was looking forward to contributing to this great project :)
> camel-mongodb write operations should put have configurable option to put WriteResult in header
> -----------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: New Feature
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Assignee: Raul Kripalani
> Priority: Minor
> Labels: features
> Fix For: 2.10.3, 2.11.0
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5696) camel-mongodb save operation should
put have configurable option to put WriteResult in header
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472692#comment-13472692 ]
Raul Kripalani commented on CAMEL-5696:
---------------------------------------
[~elihusmails],
Sounds like a reasonable enhancement.
Would you by any chance be willing to work on a patch for this one?
Thanks,
Raúl.
> camel-mongodb save operation should put have configurable option to put WriteResult in header
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Priority: Minor
> Labels: features
> Fix For: 2.11.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5696) camel-mongodb write operations should
put have configurable option to put WriteResult in header
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raul Kripalani updated CAMEL-5696:
----------------------------------
Summary: camel-mongodb write operations should put have configurable option to put WriteResult in header (was: camel-mongodb save operation should put have configurable option to put WriteResult in header)
> camel-mongodb write operations should put have configurable option to put WriteResult in header
> -----------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: New Feature
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Assignee: Raul Kripalani
> Priority: Minor
> Labels: features
> Fix For: 2.11.0, 2.10.3
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5696) camel-mongodb save operation should
put have configurable option to put WriteResult in header
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raul Kripalani updated CAMEL-5696:
----------------------------------
Fix Version/s: 2.10.2
> camel-mongodb save operation should put have configurable option to put WriteResult in header
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: New Feature
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Assignee: Raul Kripalani
> Priority: Minor
> Labels: features
> Fix For: 2.11.0, 2.10.2
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5696) camel-mongodb save operation should
put have configurable option to put WriteResult in header
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472706#comment-13472706 ]
Raul Kripalani commented on CAMEL-5696:
---------------------------------------
We could call this option {{writeResultAsHeader}} (false by default), and the header could be named {{CamelMongoDbWriteResult}}.
Not only should it apply to the save operation, but also to all write operations in general.
Beware that the result is always returned in an OUT message, and this must remain unchanged to preserve endpoint semantics. If {{writeResultAsHeader}} is enabled, we would copy the IN body to the OUT body.
In fact, now that I look at the source, the camel-mongodb component should also transfer all headers from the IN message to the OUT message. Currently they I think are lost.
> camel-mongodb save operation should put have configurable option to put WriteResult in header
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Priority: Minor
> Labels: features
> Fix For: 2.11.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5696) camel-mongodb save operation should
put have configurable option to put WriteResult in header
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-5696:
-----------------------------------
Fix Version/s: (was: 2.10.2)
2.10.3
> camel-mongodb save operation should put have configurable option to put WriteResult in header
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: New Feature
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Assignee: Raul Kripalani
> Priority: Minor
> Labels: features
> Fix For: 2.11.0, 2.10.3
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CAMEL-5696) camel-mongodb save operation
should put have configurable option to put WriteResult in header
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472706#comment-13472706 ]
Raul Kripalani edited comment on CAMEL-5696 at 10/9/12 8:14 PM:
----------------------------------------------------------------
We could call this option {{writeResultAsHeader}} (false by default), and the header could be named {{CamelMongoDbWriteResult}}.
Not only should it apply to the save operation, but also to all write operations in general.
Beware that the result is always returned in an OUT message, and this must remain unchanged to preserve endpoint semantics. If {{writeResultAsHeader}} is enabled, we would copy the IN body to the OUT body.
In fact, now that I look at the source, the camel-mongodb component should also transfer all headers from the IN message to the OUT message. Currently I think they are lost.
was (Author: raulvk):
We could call this option {{writeResultAsHeader}} (false by default), and the header could be named {{CamelMongoDbWriteResult}}.
Not only should it apply to the save operation, but also to all write operations in general.
Beware that the result is always returned in an OUT message, and this must remain unchanged to preserve endpoint semantics. If {{writeResultAsHeader}} is enabled, we would copy the IN body to the OUT body.
In fact, now that I look at the source, the camel-mongodb component should also transfer all headers from the IN message to the OUT message. Currently they I think are lost.
> camel-mongodb save operation should put have configurable option to put WriteResult in header
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Priority: Minor
> Labels: features
> Fix For: 2.11.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5696) camel-mongodb save operation should
put have configurable option to put WriteResult in header
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raul Kripalani updated CAMEL-5696:
----------------------------------
Assignee: Raul Kripalani
Issue Type: New Feature (was: Improvement)
Remaining Estimate: 0h (was: 48h)
Original Estimate: 0h (was: 48h)
> camel-mongodb save operation should put have configurable option to put WriteResult in header
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: New Feature
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Assignee: Raul Kripalani
> Priority: Minor
> Labels: features
> Fix For: 2.11.0, 2.10.2
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5696) camel-mongodb save operation should
put have configurable option to put WriteResult in header
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473666#comment-13473666 ]
Raul Kripalani commented on CAMEL-5696:
---------------------------------------
[~elihusmails], I'm already working on this one. No need to contribute a patch. Thanks.
> camel-mongodb save operation should put have configurable option to put WriteResult in header
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: New Feature
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Assignee: Raul Kripalani
> Priority: Minor
> Labels: features
> Fix For: 2.11.0, 2.10.2
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5696) camel-mongodb write operations
should put have configurable option to put WriteResult in header
Posted by "Raul Kripalani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raul Kripalani resolved CAMEL-5696.
-----------------------------------
Resolution: Fixed
> camel-mongodb write operations should put have configurable option to put WriteResult in header
> -----------------------------------------------------------------------------------------------
>
> Key: CAMEL-5696
> URL: https://issues.apache.org/jira/browse/CAMEL-5696
> Project: Camel
> Issue Type: New Feature
> Components: camel-mongodb
> Affects Versions: 2.10.1
> Environment: Windows 7, Camel 2.10.1, MongoDB 2.7.3
> Reporter: Mark Webb
> Assignee: Raul Kripalani
> Priority: Minor
> Labels: features
> Fix For: 2.11.0, 2.10.3
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I would like a configurable option to put the WriteResult from a mongodb save into the Exchange header and keep the input message to be the same as the output message.
> If a user wants to put the update in the processing of data and continue more processing of the data they won't be able to do so because the data is lost and replaced with a WriteResult object.
> There are EIP workarounds for this, but a simple configuration option would work in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira