# Partition Field Type Enum Docs-vs-Spec Disagreement > Source-anchored research for Partition Field Type Enum Docs-vs-Spec Disagreement. Run status: COMPLETED. Parent: [Online Archive partition-field selection](https://llms-explorer.com/tree/online-archive-partition-field-selection/) · 3 facets · 9 facts · page: https://llms-explorer.com/tree/partition-field-type-enum-docs-vs-spec-disagreement/ ## Problems, failure modes and limitations - Pulumi OnlineArchive documentation repeats the six-value field-type list and the UUID subtype caveat; it does not independently demonstrate runtime behavior. (medium confidence) (verified as of 2026-10-14) — [source](https://www.pulumi.com/registry/packages/mongodbatlas/api-docs/onlinearchive/) ## Comparisons and alternatives - In the inspected Terraform implementation, partition_fields.field_type has Computed: true and is not Optional or Required. The generated schema mirror marks PartitionFieldView.fieldType readOnly: true and requires fieldName and order instead. Together these artifacts indicate returned or inferred metadata rather than a normal configurable enum; the mirror is secondary evidence and does not prove current request behavior. (medium confidence) (verified as of 2026-10-14) — [source](https://raw.githubusercontent.com/mongodb/terraform-provider-mongodbatlas/master/internal/service/onlinearchive/resource.go) ## Facts and statements - The standard and time-series configuration guides list partition attribute types date, double, int, long, objectId, string, and boolean; neither list includes uuid. (high confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/online-archive/configure-online-archive-standard.md) - The 2024-11-13 Return One Online Archive reference and Terraform resource documentation list fieldType values date, int, long, objectId, string, and uuid, omitting double and boolean. (high confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-11-13/operation/operation-getgroupclusteronlinearchive) - The standard-collection guide lists partition attribute types date, double, int, long, objectId, string and boolean, whereas the Admin API v2 2024-11-13 GET response lists fieldType values date, int, long, objectId, string and uuid. Their documented intersection is date, int, long, objectId and string; double and boolean occur only in the guide list, and uuid only in the API list. This establishes a documentation mismatch, not a measured server rejection. (high confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/atlas/online-archive/configure-online-archive-standard.md) - The API fieldType description and Terraform resource documentation both specify UUID binary subtype 4 and say UUID subtype 3 partition parameters are skipped. This is a documented restriction; no live archive test was performed. (high confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-11-13/operation/operation-getgroupclusteronlinearchive) - Crossplane provider-mongodbatlas v1.4.2 places FieldType in PartitionFieldsObservation; PartitionFieldsParameters and PartitionFieldsInitParameters expose FieldName and Order without FieldType. Thus this generated provider surface does not offer fieldType as a partition input. (medium confidence) (verified as of 2026-09-10) — [source](https://pkg.go.dev/github.com/crossplane-contrib/provider-mongodbatlas%40v1.4.2/apis/namespaced/mongodbatlas/v1alpha1) - Terraform resource documentation and the Pulumi OnlineArchive page repeat the six-value API list date, int, long, objectId, string and uuid. The inspected Crossplane v1.4.2 generated type comment repeats it too. These are downstream references to the same MongoDB contract and do not establish three independent observations of backend support. (medium confidence) (verified as of 2026-10-14) — [source](https://raw.githubusercontent.com/mongodb/terraform-provider-mongodbatlas/master/docs/resources/online_archive.md) - The standard-collection guide says Atlas determines a partition field type by sampling 10 documents and does not archive documents whose selected field value does not match other documents in the collection. Therefore a supported-type label alone does not establish that a polymorphic field is suitable for partitioning. (low confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/atlas/online-archive/configure-online-archive-standard.md)