Aws DynamoDB DAX Scan table












0















Using rowMapper Configuration and using new ClientConfig()
and AmazonDaxClient



I'm facing trouble syncing the dax cluster with my table(s). I know that I have to go through a double hop to get back the query results if it had been updated around the dax in-memory cache. To work around this problem when I have already large amounts of data written like this, How would I sync it to my DAX Cluster without a client querying it?



So, I thought of doing a throttled table scan connected to my dax endpoint.
This is only returning in-cache objects only. No updates/insertions are being reflected via the table scan through the dax.



Any help?










share|improve this question



























    0















    Using rowMapper Configuration and using new ClientConfig()
    and AmazonDaxClient



    I'm facing trouble syncing the dax cluster with my table(s). I know that I have to go through a double hop to get back the query results if it had been updated around the dax in-memory cache. To work around this problem when I have already large amounts of data written like this, How would I sync it to my DAX Cluster without a client querying it?



    So, I thought of doing a throttled table scan connected to my dax endpoint.
    This is only returning in-cache objects only. No updates/insertions are being reflected via the table scan through the dax.



    Any help?










    share|improve this question

























      0












      0








      0








      Using rowMapper Configuration and using new ClientConfig()
      and AmazonDaxClient



      I'm facing trouble syncing the dax cluster with my table(s). I know that I have to go through a double hop to get back the query results if it had been updated around the dax in-memory cache. To work around this problem when I have already large amounts of data written like this, How would I sync it to my DAX Cluster without a client querying it?



      So, I thought of doing a throttled table scan connected to my dax endpoint.
      This is only returning in-cache objects only. No updates/insertions are being reflected via the table scan through the dax.



      Any help?










      share|improve this question














      Using rowMapper Configuration and using new ClientConfig()
      and AmazonDaxClient



      I'm facing trouble syncing the dax cluster with my table(s). I know that I have to go through a double hop to get back the query results if it had been updated around the dax in-memory cache. To work around this problem when I have already large amounts of data written like this, How would I sync it to my DAX Cluster without a client querying it?



      So, I thought of doing a throttled table scan connected to my dax endpoint.
      This is only returning in-cache objects only. No updates/insertions are being reflected via the table scan through the dax.



      Any help?







      amazon-web-services amazon-dynamodb amazon-dynamodb-dax






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 6:49









      Siddarth SreeniSiddarth Sreeni

      338112




      338112
























          1 Answer
          1






          active

          oldest

          votes


















          0














          What is your TTL configured for Query Cache?
          The reason why you might be seeing this behavior is that the table scan is getting a cache hit, hence DAX wouldn't contact DynamoDB. Consequently, you would get old data. This data would be stale till the time of your TTL for Query Cache and then subsequent query would get new data.



          To read more about Item cache and Query cache, you can visit DAX's official page: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.concepts.html#DAX.concepts.query-cache






          share|improve this answer
























          • TTL for QueryCache is less than a minute. And I try to do a scan and it still returns me whatever is in the dax only. Meaning. DAX isnt getting updated on SCANs

            – Siddarth Sreeni
            Nov 19 '18 at 7:05











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53275333%2faws-dynamodb-dax-scan-table%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          What is your TTL configured for Query Cache?
          The reason why you might be seeing this behavior is that the table scan is getting a cache hit, hence DAX wouldn't contact DynamoDB. Consequently, you would get old data. This data would be stale till the time of your TTL for Query Cache and then subsequent query would get new data.



          To read more about Item cache and Query cache, you can visit DAX's official page: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.concepts.html#DAX.concepts.query-cache






          share|improve this answer
























          • TTL for QueryCache is less than a minute. And I try to do a scan and it still returns me whatever is in the dax only. Meaning. DAX isnt getting updated on SCANs

            – Siddarth Sreeni
            Nov 19 '18 at 7:05
















          0














          What is your TTL configured for Query Cache?
          The reason why you might be seeing this behavior is that the table scan is getting a cache hit, hence DAX wouldn't contact DynamoDB. Consequently, you would get old data. This data would be stale till the time of your TTL for Query Cache and then subsequent query would get new data.



          To read more about Item cache and Query cache, you can visit DAX's official page: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.concepts.html#DAX.concepts.query-cache






          share|improve this answer
























          • TTL for QueryCache is less than a minute. And I try to do a scan and it still returns me whatever is in the dax only. Meaning. DAX isnt getting updated on SCANs

            – Siddarth Sreeni
            Nov 19 '18 at 7:05














          0












          0








          0







          What is your TTL configured for Query Cache?
          The reason why you might be seeing this behavior is that the table scan is getting a cache hit, hence DAX wouldn't contact DynamoDB. Consequently, you would get old data. This data would be stale till the time of your TTL for Query Cache and then subsequent query would get new data.



          To read more about Item cache and Query cache, you can visit DAX's official page: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.concepts.html#DAX.concepts.query-cache






          share|improve this answer













          What is your TTL configured for Query Cache?
          The reason why you might be seeing this behavior is that the table scan is getting a cache hit, hence DAX wouldn't contact DynamoDB. Consequently, you would get old data. This data would be stale till the time of your TTL for Query Cache and then subsequent query would get new data.



          To read more about Item cache and Query cache, you can visit DAX's official page: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.concepts.html#DAX.concepts.query-cache







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 16 '18 at 0:51









          Dishant KapadiyaDishant Kapadiya

          419410




          419410













          • TTL for QueryCache is less than a minute. And I try to do a scan and it still returns me whatever is in the dax only. Meaning. DAX isnt getting updated on SCANs

            – Siddarth Sreeni
            Nov 19 '18 at 7:05



















          • TTL for QueryCache is less than a minute. And I try to do a scan and it still returns me whatever is in the dax only. Meaning. DAX isnt getting updated on SCANs

            – Siddarth Sreeni
            Nov 19 '18 at 7:05

















          TTL for QueryCache is less than a minute. And I try to do a scan and it still returns me whatever is in the dax only. Meaning. DAX isnt getting updated on SCANs

          – Siddarth Sreeni
          Nov 19 '18 at 7:05





          TTL for QueryCache is less than a minute. And I try to do a scan and it still returns me whatever is in the dax only. Meaning. DAX isnt getting updated on SCANs

          – Siddarth Sreeni
          Nov 19 '18 at 7:05


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53275333%2faws-dynamodb-dax-scan-table%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Full-time equivalent

          Bicuculline

          さくらももこ