Phloem transport limitation in Huanglongbing-affected sweet orange is dependent on phloem-limited bacteria and callose.

Huanglongbing (HLB), caused by Candidatus `Liberibacter asiaticus' (CLas), is a phloem-limited disease that disrupts citrus production in affected areas. In HLB-affected plants, phloem sieve plate pores accumulate callose, and leaf carbohydrate export is reduced. However, whether HLB causes a reduction in carbohydrate phloem translocation speed and the quantitative relationships among callose, CLas population and phloem translocation are still unknown. In this work, a procedure was developed to concurrently measure sugar transport, callose deposition and relative pathogen population at different locations throughout the stem. Increasing quantities of CLas genetic material were positively correlated with quantity and density of callose deposits and negatively correlated with phloem translocation speed. Callose deposit quantity was position and rootstock dependent and was negatively correlated with phloem translocation speed, suggesting a localized relationship. Remarkably, callose accumulation and phloem translocation disruption in the scion were dependent on rootstock genotype. Regression results suggested that the interaction of Ct values and number of phloem callose depositions, but not their size or density, explained the effects on translocation speed. Sucrose, starch and sink 14C label allocation data support the interpretation of a transport pathway limitation by CLas infection. This work shows that the interaction of local accumulation of callose and CLas affects phloem transport. Furthermore, the extent of this accumulation is attenuated by the rootstock and provides important information about the disease mechanism of phloem-inhabiting bacteria. Together, these results constitute the first example of a demonstrated transport limitation of phloem function by a microbial infection.

Informations de copyright

© The Author(s) 2021. Published by Oxford University Press. All rights reserved. For permissions, please e-mail: [e-mail].