{"id":33,"date":"2015-09-29T21:53:14","date_gmt":"2015-09-29T21:53:14","guid":{"rendered":"http:\/\/nenadnoveljic.com\/blog\/?p=33"},"modified":"2016-01-06T21:04:19","modified_gmt":"2016-01-06T21:04:19","slug":"temp-table-transformation-and-sql-plan-directives","status":"publish","type":"post","link":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/","title":{"rendered":"Temp table transformation and SQL plan directives"},"content":{"rendered":"

Introduction<\/h4>\n

Temp temporary transformation is the operation in the execution plan where Oracle stores the subquery results in a temporary table. Cardinality estimates can get different if the temp table transformation is used in Oracle 12c. The purpose of this post is to explain why this happens.<\/p>\n

Test data<\/h4>\n

To prove the point, we will first create the test table t with unevenly populated column value<\/em>:<\/p>\n

create table t as\r\nSELECT level id,'UNPOPULAR VALUE' value\r\nFROM   dual\r\nCONNECT BY level <= 10;\r\n\r\ninsert into t\r\nSELECT level,'POPULAR_VALUE'\r\nFROM   dual\r\nCONNECT BY level <= 90;\r\n\r\ncommit ;\r\n\r\nEXEC DBMS_STATS.gather_table_stats('SYS', 'T');<\/pre>\n
First execution ( just to create SQL plan directive )<\/h4>\n
Subsequently, we will execute the following query, which selects unpopular values.<\/p>\n
SELECT \/*+ GATHER_PLAN_STATISTICS *\/ * \r\n  FROM   t \r\n  WHERE  value = 'UNPOPULAR VALUE' and id >= 1 ;\r\n\r\n<\/pre>\n
Because of the missing histograms, the cardinality estimate is obviously wrong (50 rows estimated vs. 10 actual rows):<\/p>\n
------------------------------------------------------------------------------------\r\n| Id  | Operation         | Name | Starts | E-Rows | A-Rows |   A-Time   | Buffers |\r\n------------------------------------------------------------------------------------\r\n|   0 | SELECT STATEMENT  |      |      1 |        |     10 |00:00:00.01 |       5 |\r\n|*  1 |  TABLE ACCESS FULL| T    |      1 |     50 |     10 |00:00:00.01 |       5 |\r\n------------------------------------------------------------------------------------\r\n<\/pre>\n
However, because of the \u201cAND\u201d clause in the filter predicate, the statistics feedback kicked in and as a result, the SQL plan directive was created, which we will persist with the following statement:<\/p>\n
EXEC DBMS_SPD.flush_sql_plan_directive;<\/pre>\n
This means, that the second execution should yield correct cardinality estimates, which indeed happens:<\/p>\n
SELECT \/*+ GATHER_PLAN_STATISTICS *\/ * \r\n  FROM   t e2 \r\n  WHERE  value = 'UNPOPULAR VALUE' and id >= 1 ;\r\n<\/pre>\n
------------------------------------------------------------------------------------\r\n| Id  | Operation         | Name | Starts | E-Rows | A-Rows |   A-Time   | Buffers |\r\n------------------------------------------------------------------------------------\r\n|   0 | SELECT STATEMENT  |      |      1 |        |     10 |00:00:00.01 |       5 |\r\n|*  1 |  TABLE ACCESS FULL| T    |      1 |     10 |     10 |00:00:00.01 |       5 |\r\n------------------------------------------------------------------------------------\r\n\r\nPredicate Information (identified by operation id):\r\n---------------------------------------------------\r\n\r\n   1 - filter((\"VALUE\"='UNPOPULAR VALUE' AND \"ID\">=1))\r\n\r\nNote\r\n-----\r\n   - statistics feedback used for this statement\r\n<\/pre>\n
Temp table transformation<\/h4>\n
In the next step, the query is slightly rewritten, to establish the baseline which will be compared afterwards with the query, which uses temp table transformation:<\/p>\n
select * from \r\n(with q as ( \r\n  select * \r\n    from t \r\n    where value='UNPOPULAR VALUE' and id>= 1\r\n) \r\nselect \/*+ GATHER_PLAN_STATISTICS *\/ * from q \r\n) ;\r\n<\/pre>\n
It can be seen, that the cardinality estimate is still correct:<\/p>\n
------------------------------------------------------------------------------------\r\n| Id  | Operation         | Name | Starts | E-Rows | A-Rows |   A-Time   | Buffers |\r\n------------------------------------------------------------------------------------\r\n|   0 | SELECT STATEMENT  |      |      1 |        |     10 |00:00:00.01 |       5 |\r\n|*  1 |  TABLE ACCESS FULL| T    |      1 |     10 |     10 |00:00:00.01 |       5 |\r\n<\/pre>\n
Finally, we will enforce the temp table transformation\u00a0by using the undocumented materialize hint:<\/p>\n
select * from \r\n(with q as ( \r\n  select \/*+ materialize *\/ * \r\n    from t \r\n    where value='UNPOPULAR VALUE' and id>= 1\r\n) \r\nselect \/*+ GATHER_PLAN_STATISTICS *\/ * from q \r\n);\r\n<\/pre>\n
The estimated cardinality is wrong now:<\/p>\n
---------------------------------------------------------------------------------------------------------------------------------------\r\n| Id  | Operation                   | Name                        | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads  | Writes |\r\n---------------------------------------------------------------------------------------------------------------------------------------\r\n|   0 | SELECT STATEMENT            |                             |      1 |        |     10 |00:00:00.01 |      20 |      1 |      1 |\r\n|   1 |  VIEW                       |                             |      1 |     50 |     10 |00:00:00.01 |      20 |      1 |      1 |\r\n|   2 |   TEMP TABLE TRANSFORMATION |                             |      1 |        |     10 |00:00:00.01 |      20 |      1 |      1 |\r\n|   3 |    LOAD AS SELECT           |                             |      1 |        |      0 |00:00:00.01 |       8 |      0 |      1 |\r\n|*  4 |     TABLE ACCESS FULL       | T                           |      1 |     10 |     10 |00:00:00.01 |       4 |      0 |      0 |\r\n|   5 |    VIEW                     |                             |      1 |     50 |     10 |00:00:00.01 |       7 |      1 |      0 |\r\n|   6 |     TABLE ACCESS FULL       | SYS_TEMP_0FD9D6F66_B0C71D84 |      1 |     50 |     10 |00:00:00.01 |       7 |      1 |      0 |\r\n---------------------------------------------------------------------------------------------------------------------------------------\r\n<\/pre>\n
The reason for this phenomena can be found by comparing the relevant sections in 10053 trace.<\/p>\n
Without temp table transformation, there is a SQL plan directive for dynamic sampling of the T table, which adjusts the originally\u00a0calculated\u00a0cardinality\u00a0:<\/p>\n
 SPD: Directive valid: dirid = 866821167068028328, state = 2, flags = 1, loc = 1 {C(2611393)[1, 2]}\r\n  SPD: Return code in qosdDSDirSetup: EXISTS, estType = TABLE\r\n\r\nCard: Original: 100.000000    >> Single Tab Card adjusted from 50.000000 to 10.000000 due to adaptive dynamic sampling<\/pre>\n
In the execution plan with the temp table transformation such directive is missing for the temporary table SYS_TEMP_0FD9D6F66_B0C71D84:<\/p>\n
Access path analysis for SYS_TEMP_0FD9D6F65_B0C71D84\r\n***************************************\r\nSINGLE TABLE ACCESS PATH\r\n\u00a0 Single Table Cardinality Estimation for SYS_TEMP_0FD9D6F65_B0C71D84[T1]\r\n\u00a0 SPD: Return code in qosdDSDirSetup: NOQBCTX, estType = TABLE\r\n\u00a0 Table: SYS_TEMP_0FD9D6F65_B0C71D84\u00a0 Alias: T1\r\n\u00a0\u00a0\u00a0 Card: Original: 50.000000\u00a0 Rounded: 50\u00a0 Computed: 50.000000\u00a0 Non Adjusted: 50.000000<\/pre>\n
Curiously, Oracle sampled the T table, but it\u00a0didn’t use the data to estimate the cardinality of the temporary table:<\/p>\n
Access path analysis for T\r\n***************************************\r\nSINGLE TABLE ACCESS PATH\r\n  Single Table Cardinality Estimation for T[T]\r\n  SPD: Directive valid: dirid = 866821167068028328, state = 2, flags = 1, loc = 1 {C(2611393)[1, 2]}\r\n  SPD: Return code in qosdDSDirSetup: EXISTS, estType = TABLE\r\n\r\n  Table: T  Alias: T\r\n    Card: Original: 100.000000    >> Single Tab Card adjusted from 50.000000 to 10.000000 due to adaptive dynamic sampling\r\n  Rounded: 10  Computed: 10.000000  Non Adjusted: 50.000000\r\n<\/pre>\n
 
\n 
\nUpdate 6.1.2016: Oracle support filed a bug for this problem – Bug 22497876 : INCORRECT CARDINALITY FOR QUERY USING MATERIALIZED WITH CLAUSE AND DS DIRECTIVE<\/p>\n","protected":false},"excerpt":{"rendered":"
Temp temporary transformation is the operation in the execution plan where Oracle stores the subquery results in a temporary table. Cardinality estimates can get different if the temp table transformation is used in Oracle 12c. The purpose of this post is to explain why this happens. Continue Reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[8,10,11,5],"tags":[],"class_list":["post-33","post","type-post","status-publish","format-standard","hentry","category-12c","category-adaptive-query-optimization","category-cost-based-optimizer","category-oracle"],"yoast_head":"\nTemp table transformation and SQL plan directives<\/title>\n<meta name=\"description\" content=\"Temp temporary transformation is the operation in the execution plan where Oracle stores the subquery results in a temporary table. Cardinality estimates can get different if the temp table transformation is used in Oracle 12c. The purpose of this post is to explain why this happens.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Temp table transformation and SQL plan directives\" \/>\n<meta property=\"og:description\" content=\"Temp temporary transformation is the operation in the execution plan where Oracle stores the subquery results in a temporary table. Cardinality estimates can get different if the temp table transformation is used in Oracle 12c. The purpose of this post is to explain why this happens.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/\" \/>\n<meta property=\"og:site_name\" content=\"All-round Database Topics\" \/>\n<meta property=\"article:published_time\" content=\"2015-09-29T21:53:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2016-01-06T21:04:19+00:00\" \/>\n<meta name=\"author\" content=\"Nenad Noveljic\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@NenadNoveljic\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nenad Noveljic\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/temp-table-transformation-and-sql-plan-directives\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/temp-table-transformation-and-sql-plan-directives\\\/\"},\"author\":{\"name\":\"Nenad Noveljic\",\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/#\\\/schema\\\/person\\\/51458d9dd86dbbdd19f5add451d44efa\"},\"headline\":\"Temp table transformation and SQL plan directives\",\"datePublished\":\"2015-09-29T21:53:14+00:00\",\"dateModified\":\"2016-01-06T21:04:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/temp-table-transformation-and-sql-plan-directives\\\/\"},\"wordCount\":323,\"commentCount\":6,\"articleSection\":[\"12c\",\"adaptive query optimization\",\"cost based optimizer\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/temp-table-transformation-and-sql-plan-directives\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/temp-table-transformation-and-sql-plan-directives\\\/\",\"url\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/temp-table-transformation-and-sql-plan-directives\\\/\",\"name\":\"Temp table transformation and SQL plan directives\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/#website\"},\"datePublished\":\"2015-09-29T21:53:14+00:00\",\"dateModified\":\"2016-01-06T21:04:19+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/#\\\/schema\\\/person\\\/51458d9dd86dbbdd19f5add451d44efa\"},\"description\":\"Temp temporary transformation is the operation in the execution plan where Oracle stores the subquery results in a temporary table. Cardinality estimates can get different if the temp table transformation is used in Oracle 12c. The purpose of this post is to explain why this happens.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/temp-table-transformation-and-sql-plan-directives\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/temp-table-transformation-and-sql-plan-directives\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/temp-table-transformation-and-sql-plan-directives\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Temp table transformation and SQL plan directives\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/\",\"name\":\"All-round Database Topics\",\"description\":\"Nenad Noveljic\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/#\\\/schema\\\/person\\\/51458d9dd86dbbdd19f5add451d44efa\",\"name\":\"Nenad Noveljic\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a97b796613ea48ec8a7b79c8ffe1c685dcffc920c68121f6238d5caab5070670?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a97b796613ea48ec8a7b79c8ffe1c685dcffc920c68121f6238d5caab5070670?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a97b796613ea48ec8a7b79c8ffe1c685dcffc920c68121f6238d5caab5070670?s=96&d=mm&r=g\",\"caption\":\"Nenad Noveljic\"},\"sameAs\":[\"nenad-noveljic-9b746a6\",\"https:\\\/\\\/x.com\\\/NenadNoveljic\"],\"url\":\"https:\\\/\\\/nenadnoveljic.com\\\/blog\\\/author\\\/nenad\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Temp table transformation and SQL plan directives","description":"Temp temporary transformation is the operation in the execution plan where Oracle stores the subquery results in a temporary table. Cardinality estimates can get different if the temp table transformation is used in Oracle 12c. The purpose of this post is to explain why this happens.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/","og_locale":"en_US","og_type":"article","og_title":"Temp table transformation and SQL plan directives","og_description":"Temp temporary transformation is the operation in the execution plan where Oracle stores the subquery results in a temporary table. Cardinality estimates can get different if the temp table transformation is used in Oracle 12c. The purpose of this post is to explain why this happens.","og_url":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/","og_site_name":"All-round Database Topics","article_published_time":"2015-09-29T21:53:14+00:00","article_modified_time":"2016-01-06T21:04:19+00:00","author":"Nenad Noveljic","twitter_card":"summary_large_image","twitter_creator":"@NenadNoveljic","twitter_misc":{"Written by":"Nenad Noveljic","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/#article","isPartOf":{"@id":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/"},"author":{"name":"Nenad Noveljic","@id":"https:\/\/nenadnoveljic.com\/blog\/#\/schema\/person\/51458d9dd86dbbdd19f5add451d44efa"},"headline":"Temp table transformation and SQL plan directives","datePublished":"2015-09-29T21:53:14+00:00","dateModified":"2016-01-06T21:04:19+00:00","mainEntityOfPage":{"@id":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/"},"wordCount":323,"commentCount":6,"articleSection":["12c","adaptive query optimization","cost based optimizer","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/","url":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/","name":"Temp table transformation and SQL plan directives","isPartOf":{"@id":"https:\/\/nenadnoveljic.com\/blog\/#website"},"datePublished":"2015-09-29T21:53:14+00:00","dateModified":"2016-01-06T21:04:19+00:00","author":{"@id":"https:\/\/nenadnoveljic.com\/blog\/#\/schema\/person\/51458d9dd86dbbdd19f5add451d44efa"},"description":"Temp temporary transformation is the operation in the execution plan where Oracle stores the subquery results in a temporary table. Cardinality estimates can get different if the temp table transformation is used in Oracle 12c. The purpose of this post is to explain why this happens.","breadcrumb":{"@id":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/nenadnoveljic.com\/blog\/temp-table-transformation-and-sql-plan-directives\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/nenadnoveljic.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Temp table transformation and SQL plan directives"}]},{"@type":"WebSite","@id":"https:\/\/nenadnoveljic.com\/blog\/#website","url":"https:\/\/nenadnoveljic.com\/blog\/","name":"All-round Database Topics","description":"Nenad Noveljic","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/nenadnoveljic.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/nenadnoveljic.com\/blog\/#\/schema\/person\/51458d9dd86dbbdd19f5add451d44efa","name":"Nenad Noveljic","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a97b796613ea48ec8a7b79c8ffe1c685dcffc920c68121f6238d5caab5070670?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a97b796613ea48ec8a7b79c8ffe1c685dcffc920c68121f6238d5caab5070670?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a97b796613ea48ec8a7b79c8ffe1c685dcffc920c68121f6238d5caab5070670?s=96&d=mm&r=g","caption":"Nenad Noveljic"},"sameAs":["nenad-noveljic-9b746a6","https:\/\/x.com\/NenadNoveljic"],"url":"https:\/\/nenadnoveljic.com\/blog\/author\/nenad\/"}]}},"_links":{"self":[{"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/posts\/33","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/comments?post=33"}],"version-history":[{"count":2,"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/posts\/33\/revisions"}],"predecessor-version":[{"id":261,"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/posts\/33\/revisions\/261"}],"wp:attachment":[{"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/media?parent=33"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/categories?post=33"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nenadnoveljic.com\/blog\/wp-json\/wp\/v2\/tags?post=33"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}