Skip to content
Permalink
Browse files
use ANALYZE command, not operation
  • Loading branch information
lisakowen committed Jun 1, 2017
1 parent aaa7ebb commit a9fcece4308e51a5c1bc55b70ce3b3ef3305c5df
Showing 3 changed files with 3 additions and 3 deletions.
@@ -53,7 +53,7 @@ The HBase profile is equivalent to the following PXF parameters:
- Accessor=org.apache.hawq.pxf.plugins.hbase.HBaseAccessor
- Resolver=org.apache.hawq.pxf.plugins.hbase.HBaseResolver

**Note**: `ANALYZE` operations are not supported on external tables you create with the `HBase` profile.
**Note**: The `ANALYZE` command is not supported on external tables you create with the `HBase` profile.

## <a id="columnmapping"></a>Column Mapping

@@ -176,7 +176,7 @@ JSON-plug-in-specific keywords and values used in the `CREATE EXTERNAL TABLE` ca
| FORMAT | The `FORMAT` clause must specify `CUSTOM`. |
| FORMATTER | The JSON `CUSTOM` format supports only the built-in `pxfwritable_import` `FORMATTER`. |

**Note**: `ANALYZE` operations are not supported on external tables you create with the `Json` profile.
**Note**: The `ANALYZE` command is not supported on external tables you create with the `Json` profile.

### Example 1 <a id="jsonexample1"></a>

@@ -75,7 +75,7 @@ When `pxf_stat_max_fragments` is false, `ANALYZE` outputs a message to warn that

There may be situations where the remote statistics retrieval could fail to perform a task on a PXF table. For example, if a PXF Java component is down, the remote statistics retrieval might not occur, and the database transaction would not succeed. In these cases, the statistics remain with the default external table values.

**Note**: `ANALYZE` operations are not supported on PXF external tables created with the `HBase` or `Json` profiles.
**Note**: The `ANALYZE` command is not supported on PXF external tables created with the `HBase` or `Json` profiles.

## <a id="examples"></a>Examples

0 comments on commit a9fcece

Please sign in to comment.