Table: Unify the creation of Batch and single op requests #56

Closed
jcookems opened this Issue Apr 24, 2012 · 2 comments

Comments

Projects
None yet
2 participants
Contributor

jcookems commented Apr 24, 2012

The REST request for a single table operation (for example, updateEntity) should be the same as the MIME part of a batch request containing the same operation.

However, the current Table service implementation had two separate code paths for generating those requests:

updateEntity 
-> putOrMergeEntityCore 
    -> (code for building headers and constructing body)
batch(InsertEntityOperation)
-> createBatchRequestBody
    -> createBatchInsertOrUpdateEntityPart
        -> (code for building headers and constructing body)

To simplify the code, reduce maintenance costs, and ensure consistency between single ops and batch, both code paths should end up in the same function.

joostdenijs pushed a commit to joostdenijs/azure-sdk-for-java that referenced this issue Jan 18, 2013

Albert Cheng
Merge pull request #56 from gcheng/security
Encryption integration test

gcheng commented Feb 21, 2013

this part is actually odata.

gcheng commented Feb 21, 2013

at the time of updating these methods, will may do them. close for now.

@gcheng gcheng closed this Feb 21, 2013

jianghaolu pushed a commit to jianghaolu/azure-sdk-for-java that referenced this issue Apr 5, 2017

Albert Cheng
Merge pull request #56 from gcheng/security
Encryption integration test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment